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

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.

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

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

  1. Query authoritative server. Compare what this check establishes with the other devices in the path.
  2. Inspect recursive answer. Compare what this check establishes with the other devices in the path.
  3. 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.

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