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
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
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
- Inspect what the check asserts. Compare what this check establishes with the other devices in the path.
- Compare authority and release state. Compare what this check establishes with the other devices in the path.
- 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.