0

Ultra Low IPv6 Error

When I navigate to ping.nextnds.io, I'm getting an error for the IPv6 ultra low latency servers. Is this expected behavior?

 

Edit: Adding the link to my diagnostics 

4 replies

null
    • olivier
    • 3 yrs ago
    • Reported - view

    dns.nextdns.io is probably blocked by your network DNS

      • mlapida
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey What do you mean "network DNS"? I'm using NextDNS at the router level and on a dedicated server running DoH. When I run a "dig" on "dn1.nextdns.io", it resolves "dns1.steering.nextdns.io". If I run anther IPv6 dig on that "dns1.steering.nextdns.io", it comes up empty. I'm running Comcast internet, which isn't known for blocking things like this and I've tested on my mobile with Verizon with no luck.

      Do you have any troubleshooting tips?

      dig command and output for reference:

      ubuntu@dns02:~$ dig AAAA dns1.nextdns.io
      ; <<>> DiG 9.16.1-Ubuntu <<>> AAAA dns1.nextdns.io
      ;; global options: +cmd
      ;; Got answer:
      ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19446
      ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
      ;; OPT PSEUDOSECTION:
      ; EDNS: version: 0, flags:; udp: 4096
      ;; QUESTION SECTION:
      ;dns1.nextdns.io.        IN    AAAA
      ;; ANSWER SECTION:
      dns1.nextdns.io.    5    IN    CNAME    dns1.steering.nextdns.io.
      ;; Query time: 16 msec
      ;; SERVER: 127.0.0.1#53(127.0.0.1)
      ;; WHEN: Mon Feb 08 09:20:31 MST 2021
      ;; MSG SIZE  rcvd: 72
      
      • olivier
      • 3 yrs ago
      • Reported - view

      Mike L. our Denver ultralow PoPs do not have IPv6 support yet, that's why.

      • mlapida
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey That was my theory. Makes sense. Thank you doe confirming! 

Content aside

  • 3 yrs agoLast active
  • 4Replies
  • 180Views
  • 2 Following