OSPF DNS reachability: missing resolver loopback route
A secondary DNS server answers locally but is unreachable from a remote site. OSPF neighbours are FULL. The routing dashboard has mistaken friendship for delivery.
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: OSPFv2 lab. DNS listens on loopback 10.201.0.53/32. A transit adjacency is healthy; the service loopback is omitted from OSPF activation.
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
A secondary DNS server answers locally but is unreachable from a remote site. OSPF neighbours are FULL. The routing dashboard has mistaken friendship for delivery.
Checks to compare
- Compare RIB and LSDB. Compare what this check establishes with the other devices in the path.
- Inspect effective routing configuration. Compare what this check establishes with the other devices in the path.
- Validate a narrow lab correction. Compare what this check establishes with the other devices in the path.
Scope matters. OSPFv2 lab. DNS listens on loopback 10.201.0.53/32. A transit adjacency is healthy; the service loopback is omitted from OSPF activation.
Reveal the diagnosis, common mistakes and next action
What the evidence supports
A FULL adjacency proves neighbour state, not that every required prefix is advertised. Origin configuration and the remote LSDB identify the missing /32.
Common mistakes to avoid in this scenario
- The OSPF adjacency must be rebuilt: Clear the healthy neighbour relationship before checking the missing prefix.
- DNS zone replication is delayed: Replicate the zone again even though packets never reach the resolver loopback.
A proportionate next action
Advertise the intended loopback in the approved area and verify LSDB, RIB and DNS from remote clients.
Limits of the conclusion
An absent route can also result from filtering, area design or summarisation. Those alternatives are explicitly excluded by this lab evidence.