Selecting Optimal Location

I've noticed that new name server locations have launched near me. When running https://ping.nextdns.io, I see they are half the latency of the previous closest location. It looks as though NextDNS CLI/anycast is still defaulting to the old location.

Is there a reason this is happening? Is there any way to force the use of the closer location? 

My diagnostic logs can be found here

3replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • The ping.nextdns.io output is confusing as it shows you anycast primary/secondary PoPs. Although, those new locations are unicast only locations. As per your diag output, CLI is currently using:

    • Server: smarthost-den-1
    Like 1
      • Mike L.
      • mlapida
      • 1 yr ago
      • Reported - view

      Olivier Poitrey Thank you for clarification. Why is the diagnostic tool also running the trace route on the locations in Dallas? Is it running against the primary/secondary anycast servers, not the active lookup server? 

    • Mike L. because the diag tool goal is to diagnose anycast routing issues. Unicast steering is rarely if ever wrong.

      Like 1
Like Follow
  • 1 yr agoLast active
  • 3Replies
  • 188Views
  • 2 Following