Bad routing for anexia-ams: both IPv4 and IPv6 are routed through Vienna
From my network, anexia-ams seems to be routed through Vienna before being routed back to Amsterdam, close to where I live. Sadly, that's the one that all my DoH clients use. Note that the diag tool was using my local DoT client to resolve hostnames, so it doesn't show that anexia-ams was in use, but it does highlight the routing issues.
When I visit ping.nextdns.io using a DoH client as the resolver, it consistently shows anexia-ams (IPv6) as the one in use, and it's always the slowest Dutch server available and also slower than some servers located in Germany and England. Note that the routing through Vienna happens for both IPv4 and IPv6.
Thanks a lot for sharing the issue. I am also having the same thing for couple of time. Basically when I am trying to develop iphone app development agency for my client then I am basically using the dns and from their the problem arises.
Sweden is a long country and I'm much closer geographically to Copenhagen in Denmark.
These servers are picked by the NextDNS CLI:
- Primary server: Stockholm, distance 400 miles, latency 15-20 ms.
- Secondary server: Copenhagen, distance 20 miles, latency 2-3 ms.
■ anexia-cph 3 ms (secondary)
anexia-osl 10 ms
■ zepto-sto 18 ms (primary)
zepto-ams 19 ms
zepto-fra 25 ms
Platform ASUS-Merlin, Version 1.8.8