Troubleshoot DNS negative caching and NXDOMAIN
The record that refused to exist. At 10:02 a new A record is published for launch.ddiengineer.com. At 10:04 one office resolver still returns NXDOMAIN. The authoritative server answers correctly. Your colleague suggests creating the record again, but louder.
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: Same DNS view and query name. No DNSSEC validation failure. Times and TTLs are synthetic.
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
At 10:02 a new A record is published for launch.ddiengineer.com. At 10:04 one office resolver still returns NXDOMAIN. The authoritative server answers correctly. Your colleague suggests creating the record again, but louder.
Checks to compare
- Query authoritative server. Compare what this check establishes with the other devices in the path.
- Inspect recursive answer. Compare what this check establishes with the other devices in the path.
- Advance lab clock to 10:10. Compare what this check establishes with the other devices in the path.
Scope matters. Same DNS view and query name. No DNSSEC validation failure. Times and TTLs are synthetic.
Reveal the diagnosis, common mistakes and next action
What the evidence supports
The resolver cached the earlier NXDOMAIN for ten minutes. Six minutes remain at 10:04. The authority is already correct; waiting until expiry produces a fresh positive answer in this lab.
Common mistakes to avoid in this scenario
- Authoritative record is missing: Create duplicate records immediately.
- Confirmed network outage: Restart the gateway.
A proportionate next action
Verify the authoritative answer and cache lifetime. Avoid repeated edits to an already correct zone.
Limits of the conclusion
This proves the lab cache behaviour, not universal DNS health. Different views, forwarding and application caches can produce other symptoms.