0

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

3 replies

null
    • olivier
    • 3 yrs ago
    • Reported - view

    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
      • mlapida
      • 3 yrs 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? 

      • olivier
      • 3 yrs ago
      • Reported - view

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

Content aside

  • 3 yrs agoLast active
  • 3Replies
  • 271Views
  • 2 Following