DDIENGINEER.COM / FICTIONAL NETWORKS. REAL TROUBLESHOOTING.NO PRODUCTION SYSTEMS WERE REBOOTED.
⌕ PACKET DETECTIVE
DNS + DHCP · Advanced

Investigate stale DHCP-to-DNS update retries

The lease that rewrote history. A roaming device moves from Site A to Site B. Its DNS record changes to the new address, then reverts six minutes later. Both DHCP servers say their updates succeeded. For once, both are telling the truth.

What you’ll practise

Inspect the supplied evidence, distinguish competing explanations and choose a proportionate next action. Use the clickable topology and private notebook to keep track of your findings.

Lab scope: Synthetic two-scope environment with authorised updaters. The old site has a custom retry worker. An unexpired old lease alone does not normally prove a stale update will occur.

Validation: Fictional training scenario; not vendor-build verified. No live network access is required. Basic DNS, DHCP and IP addressing knowledge is helpful. Progress is stored in this browser.

DDIENGINEER.COM / INTERACTIVE NETWORK INVESTIGATIONS

DHCP says yes.
DNS says yesterday.

A laptop moved networks. Its name didn’t. Find out who’s telling the truth — and what you should check next.

ADVANCED · DNS + DHCP · ~8 MIN

Realistic DNS, DHCP and IPAM mysteries.
No lab setup. No production access. Just your judgement.

01 Inspect the clues02 Build your theory03 Make the call
FEATURED / PD–009DNS + DHCP
THE LAPTOP WITH YESTERDAY’S ADDRESS

New lease.
Old address.
Same confused user.

09:30 / DHCP ACK10.62.4.27 ✓↓ six minutes and three cache flushes later09:36 / DNS ANSWER10.61.4.27 ?

“Have you tried flushing it again?”
The fourth time is not a strategy.

FIELD NOTES / READ BEFORE OR AFTER THE LAB

Troubleshooting guide

Recognise the symptoms

A roaming device moves from Site A to Site B. Its DNS record changes to the new address, then reverts six minutes later. Both DHCP servers say their updates succeeded. For once, both are telling the truth.

Checks to compare

  1. Build the DNS update timeline. Compare what this check establishes with the other devices in the path.
  2. Inspect old-site worker state. Compare what this check establishes with the other devices in the path.
  3. Test retry-state validation. Compare what this check establishes with the other devices in the path.

Scope matters. Synthetic two-scope environment with authorised updaters. The old site has a custom retry worker. An unexpired old lease alone does not normally prove a stale update will occur.

Reveal the diagnosis, common mistakes and next action

What the evidence supports

Authoritative update logs show the old-site worker writing stale data after the new-site update. This fictional lab adds a reproducible custom retry defect; it does not claim that the source thread’s servers have this mechanism.

Common mistakes to avoid in this scenario

  • Cache TTL problem: Flush every recursive resolver.
  • All updates denied: Disable secure DNS updates.

A proportionate next action

Establish the current registration policy and prevent stale work from overwriting newer state. Verify the authoritative record over time before closing.

Limits of the conclusion

Do not blindly delete valid old leases or blame failover. A matching timeline and updater identity are essential.

Read the technical reference →

Browse all investigations →

Browse troubleshooting case guides →The missing networkThe gap in the alibiThe record that refused to existThe name with two addressesThe office with no vacanciesThe relay to nowhereThe duplicate that wasn’tThe suspiciously quiet subnetThe laptop with yesterday’s addressThe security upgrade that broke renewalsThe container that couldn’t find anythingThe lease that rewrote historyThe intermittent DHCP lotteryThe edit that never reached DNSThe policy inherited from upstairsThe updater with the wrong badgeThe fixed address with no nameThe duplicate in another network viewThe update at the wrong front doorThe lease with no permission slipThe reservation the partner forgotThe immortal DNS recordThe pipeline that retried yesterdayThe route that outlived its resolverThe adjacency with no routeThe domain controller nobody could findThe backup with a missing keyThe green dashboard with the wrong answerThe two masters of one recordThe zone transfer with no guest listThe inventory that stopped at page oneThe allocation raceThe redundant pair on one plugThe answer too large for the doorThe IPv6 address with nowhere to go