1

Forced ultralow/anycast

I did some tests and this seems to work. If NextDNS can confirm this to be true.

So, in DoH

a.

1.https://anycast.dns2.nextdns.io/123456/abcdef
2.https://anycast.dns1.nextdns.io/123456/abcdef
3.https://anycast.dns.nextdns.io/123456/abcdef

a. 1. Will call anycast 2
a. 2. Will call anycast 1
a. 3. Will call either anycast 1 or 2

b.

1.https://ultralow.dns2.nextdns.io/123456/abcdef
2.https://ultralow.dns1.nextdns.io/123456/abcdef
3.https://ultralow.dns.nextdns.io/123456/abcdef

b. 1. Will call ultralow 2

b. 2. Will call ultralow 1

b. 3. Will call either ultralow 1 or 2

Is this true?

For DoT, is there something similar? I tried the same but it didn't work.

I have dns2 on serverwala-buh and dns1 on estnoc-buh from my tests.

"status": "ok",
"protocol": "DOH",
"configuration": "",
"client": "",
"destIP": "194.68.44.36",
"anycast": false,
"server": "serverwala-buh-1",
"clientName": "unknown-doh",
"deviceName": "AdGuardHTTPS",
"deviceID": ""

For some reason anycast is connecting only on Frankfurt even if it's never fastest. Ultralow is working amazing.

estnoc-buh                0 ms  (ultralow1)  
serverwala-buh (IPv6)     0 ms
■ serverwala-buh            1 ms  (ultralow2)  
zepto-sof                25 ms  
anexia-vie               28 ms (anycast2)  
anexia-vie (IPv6)        28 ms  (anycast2)  
exoscale-vie             29 ms  
anexia-sof               31 ms  
anexia-sof (IPv6)        35 ms   exoscale-vie (IPv6)      38 ms   zepto-waw (IPv6)         44 ms   anexia-waw               46 ms  
anexia-waw (IPv6)        46 ms   zepto-waw                48 ms   premiumrdp-ist           52 ms   edgeuno-ist (IPv6)       54 ms   zepto-sto                55 ms  (anycast1)  
zepto-sto (IPv6)         57 ms  (anycast1)   edgeuno-ist              92 ms  
dns1.nextdns.io (IPv6) error (ultralow1)
dns2.nextdns.io (IPv6) error (ultralow2)

5replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • This is slightly more complex that that. All [*.]dns[1|2].nextdns.io hostnames are ultralow except anycast.$ which is a convenient hostname used by test.nextdns.io to test anycast. From there, any DoH or DoT client should use ultralow by default if they use the system DNS to resolve the dns.nextdns.io hostname. Some clients require that you provide a bootstrap IP (mostly DoT clients on routers). For these, ultralow is not an option and anycast will always be used.

    In the case of more advanced clients supporting the new HTTPS DNS record (mainly our cli and apple devices so far), ultralow will be used by default with a fallback to anycast for extra safety (which primary/secondary in each case, which gives you a tally of 4 paths). Our CLI will also use some more advanced tricks to ensure best steering and maximum resiliency.

    Finally dns1/dns2 are convenient hostnames to force only primary or secondary. For the record, primary and secondary (for anycast and ultralow) are operated on different networks with a different set of hosting providers and shifted rollout waves. All our regions have a primary and secondary point of presence.

    Like 4
      • losnad
      • losnad
      • 10 days ago
      • Reported - view

      I did had my NextDNS v6 configuration as bootstrap, I tried without it and still go to Frankfurt.

      Like
  • Anycast go to the default IPs

    Anycast1

    "status": "ok",
    "protocol": "DOH",
    "destIP": "45.90.28.0",
    "anycast": true,
    "server": "zepto-fra-1",
    "clientName": "unknown-doh",
    "deviceName": "AdGuardHTTPS",
    
    Anycast2
    "status": "ok",
    "protocol": "DOH",
    "destIP": "45.90.30.0",
    "anycast": true,
    "server": "anexia-fra-1",
    "clientName": "unknown-doh",
    "deviceName": "AdGuardHTTPS",
    
    Ultralow go to the local POPs
    
    Ultralow1
    
    "status": "ok",
    "protocol": "DOH",
    "destIP": "152.89.161.16",
    "anycast": false,
    "server": "estnoc-buh-1",
    "clientName": "unknown-doh",
    "deviceName": "AdGuardHTTPS",
    
    Ultralow2
    
    "status": "ok",
    "protocol": "DOH",
    "destIP": "194.68.44.36",
    "anycast": false,
    "server": "serverwala-buh-1",
    "clientName": "unknown-doh",
    "deviceName": "AdGuardHTTPS",
    

    I still don't understand why anycast is stuck on Frankfurt but now that I can use local ultralow I don't even care. 😂

    Like
  • for some reason anycast has better speed than ultralow for me 

    Like
      • losnad
      • losnad
      • yesterday
      • Reported - view

      Some reason might be the distance and/or the internet interconnected nodes. If you have anycast in close proximity and the ultralow is hundreds of kilometers away...

      Like
Like1 Follow
  • 1 Likes|like
  • yesterdayLast active
  • 5Replies
  • 194Views
  • 4 Following