Troubleshoot Windows DHCP and stale DNS records
The laptop with yesterday’s address. A laptop moves from wired LAN to Wi-Fi. It receives 10.62.4.27, yet laptop27.ddiengineer.com resolves to its old wired address. The user has flushed the cache three times. They are considering a fourth, for luck.
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: Windows AD-integrated secure-update zone; synthetic record and ACL data. The DHCP lease completes successfully. No live domain queries are made.
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 laptop moves from wired LAN to Wi-Fi. It receives 10.62.4.27, yet laptop27.ddiengineer.com resolves to its old wired address. The user has flushed the cache three times. They are considering a fourth, for luck.
Checks to compare
- Compare authority and cache. Compare what this check establishes with the other devices in the path.
- Inspect update failure and ACL. Compare what this check establishes with the other devices in the path.
- Test a scoped lab correction. Compare what this check establishes with the other devices in the path.
Scope matters. Windows AD-integrated secure-update zone; synthetic record and ACL data. The DHCP lease completes successfully. No live domain queries are made.
Reveal the diagnosis, common mistakes and next action
What the evidence supports
The authority itself held the old address, and the intended updater was explicitly denied by the record ACL. The scoped lab correction restored the update. This case deliberately supplies the permissions evidence rather than inferring ownership from symptoms alone.
Common mistakes to avoid in this scenario
- Positive cache TTL: Wait for cached data to expire everywhere.
- Secure updates are broken: Enable insecure updates for the entire zone.
A proportionate next action
Reconcile the intended registration policy, update credentials and effective record permissions. Verify authoritative A/PTR state as applicable and test new connections.
Limits of the conclusion
Do not assume all stale records are ACL problems. Replication, client registration policy, multiple interfaces and caching are alternative causes in other environments.