Two nearby DNS answers do not guarantee nearest-server routing
Vincent Bernat’s GeoDNS migration exposes a routing trap: returning two nearby server addresses does not tell a DNS resolver which one to prefer, because it may reorder them. His final configuration returns two addresses when their distances are similar and otherwise returns just the closest, trading some immediate failover flexibility for more predictable geographic routing.
Vincent Bernat · Nov 6, 2026
Why it matters
DNS response order is a fragile place to encode traffic preferences.
More context
The article follows a deployment of seven NixOS servers moving from Route 53 to Bunny. The final approach uses a two-minute TTL. Read it as a configuration case study, then inspect actual answers from several locations before copying the policy.
Keep in mind
Geographic distance is an approximation, cached DNS answers delay changes, and this personal deployment is not a controlled comparison of provider performance.
Original read