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.
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.
Realistic DNS, DHCP and IPAM mysteries.
No lab setup. No production access. Just your judgement.
New lease.
Old address.
Same confused user.
10.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.
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
- Build the DNS update timeline. Compare what this check establishes with the other devices in the path.
- Inspect old-site worker state. Compare what this check establishes with the other devices in the path.
- 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.