DDIENGINEER.COM / FICTIONAL NETWORKS. REAL TROUBLESHOOTING.NO PRODUCTION SYSTEMS WERE REBOOTED.
⌕ PACKET DETECTIVE
DNS + OBSERVABILITY / ADVANCED

DNS monitoring: NOERROR with the wrong answer

DNS monitoring reports 100% availability while clients connect to an old application endpoint. Every monitored query received an answer. It just was not the right answer.

What you’ll practise

Trace the supplied evidence, challenge alternative explanations, and choose a safe next action. Use the topology and private notebook to document your reasoning.

Lab scope: Synthetic migration with an approved expected-answer set and internal client probe. Expected record changed through an authorised release.

Validation: Original synthetic operational lab; not a reproduced vendor defect

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

DNS monitoring reports 100% availability while clients connect to an old application endpoint. Every monitored query received an answer. It just was not the right answer.

Checks to compare

  1. Inspect what the check asserts. Compare what this check establishes with the other devices in the path.
  2. Compare authority and release state. Compare what this check establishes with the other devices in the path.
  3. Test a correctness-aware check. Compare what this check establishes with the other devices in the path.

Scope matters. Synthetic migration with an approved expected-answer set and internal client probe. Expected record changed through an authorised release.

Reveal the diagnosis, common mistakes and next action

What the evidence supports

Receiving a valid response is different from receiving intended data. The supplied release manifest makes the wrong answer objectively testable.

Common mistakes to avoid in this scenario

  • DNS latency proves the service is healthy: Keep the current check because it returns NOERROR quickly.
  • Every client cache is stale: Flush client caches without comparing the returned RRset to the expected value.

A proportionate next action

Restore intended authoritative data through change control, then add expected-answer probes from relevant client paths.

Limits of the conclusion

Do not hardcode one address for intentionally dynamic responses. Define appropriate assertions for the service and DNS view.

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