Anycast DNS troubleshooting: BGP service-health withdrawal
One office gets DNS timeouts while another resolves normally through the same Anycast address. Both sites still advertise it. The routers would like to be excluded from the incident.
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: Two internal Anycast resolver instances announce 10.200.0.53/32 using BGP. Clients at each office prefer the nearer site. No external prefix propagation is permitted.
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
One office gets DNS timeouts while another resolves normally through the same Anycast address. Both sites still advertise it. The routers would like to be excluded from the incident.
Checks to compare
- Identify the serving paths. Compare what this check establishes with the other devices in the path.
- Compare service and route health. Compare what this check establishes with the other devices in the path.
- Test controlled withdrawal. Compare what this check establishes with the other devices in the path.
Scope matters. Two internal Anycast resolver instances announce 10.200.0.53/32 using BGP. Clients at each office prefer the nearer site. No external prefix propagation is permitted.
Reveal the diagnosis, common mistakes and next action
What the evidence supports
Per-node queries establish a failed DNS service at E while BGP still sends clients there. Controlled withdrawal restores the affected path without changing zone data.
Common mistakes to avoid in this scenario
- The shared address is unreachable: Remove both sites’ BGP advertisements because DNS fails in East.
- East clients have a stale DNS cache: Flush client caches; leave the service advertisement unchanged.
A proportionate next action
Withdraw only the failed instance’s service route using the approved procedure; add service-aware checks and recovery hysteresis.
Limits of the conclusion
Anycast is not inherently self-healing. This case supplies path and node evidence; route changes require capacity and convergence validation.