0

NextDNS suddenly stopped working

Hi, 

I've been using NextDNS Pro for around four years and my account is in good order.

The service just seems to have stopped working for no apparent reason and I can't figure out why. There have been no changes at my end (Unifi UDM). if I try to dig or use nslookup to query the DNS servers linked to my account, I get a timeout. I'm generally unable to access nextdns.io domains and had to use a VPN to log this. Swapping DNS on my router to Cloudflare, Google or quad9 works just fine.

I'm completely out of ideas for troubleshooting this one, so if anyone has any suggestions - please share!  

(UK/Vodafone)

Thanks in advance

FB

6 replies

null
    • NextDNs
    • 4 days ago
    • Reported - view

    Can you please provide a https://nextdns.io/diag?

      • Edmarfarias
      • 3 days ago
      • Reported - view

       NextDNS is somehow blocking media from downloading in WhatsApp when using mobile data. I’m using Claro carrier - Brazil 

      • Eudes
      • 2 days ago
      • Reported - view

      Claro seems to be blocking NextDNS on their mobile network

      https://help.nextdns.io/t/60ypcfy/nextdns-doesnt-work-on-claro-brazil-mobile-network

      • Edmarfarias
      • 2 days ago
      • Reported - view

       I completely gave up on trying to make it work. I uninstalled the profile. It was driving me nuts. 

    • jdoss
    • yesterday
    • Reported - view

    I am seeing the same thing from Chicago with my UDM Pro. I am getting super slow page loads on my workstation and my Android phone's wifi will report that it cannot access DNS so it fails over to LTE. Switching to 8.8.8.8 on my workstation results in everything working as expected. 

    Using 8.8.8.8 everything works
    https://nextdns.io/diag/5e3d1510-172b-11f1-90a9-c708c7df29df

    Using 45.90.28.108, 45.90.30.108 results in failures 

     

    $ sh -c 'sh -c "$(curl -s https://nextdns.io/diag)"'
Welcome to NextDNS network diagnostic tool.
This tool will download a small binary to capture latency and routing information
regarding the connectivity of your network with NextDNS. In order to perform a
traceroute, root permission is required. You may therefore be asked to provide
your password for sudo.
The source code of this tool is available at https://github.com/nextdns/diag
Do you want to continue? (press enter to accept)
Resolvers:  45.90.28.108, 45.90.30.108
Testing IPv6 connectivity
  available: false
Fetching https://test.nextdns.io
  Fetch error: Get "https://test.nextdns.io": dial tcp: lookup test.nextdns.io on 127.0.0.53:53: read udp 192.168.1.11:41056->45.90.28.108:53: i/o timeout
Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp: lookup ipv4.dns1.nextdns.io on 127.0.0.53:53: read udp 192.168.1.11:43758->45.90.28.108:53: i/o timeout
Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp: lookup ipv4.dns2.nextdns.io on 127.0.0.53:53: read udp 192.168.1.11:54617->45.90.28.108:53: i/o timeout
Fetching PoP name for anycast primary IPv4 (45.90.28.0)
  edgeuno-rio: 472.448ms
Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
  anexia-chi: 12.463ms
Pinging PoPs
  error: Get "https://router.nextdns.io/?limit=10&stack=dual": dial tcp: lookup router.nextdns.io on 127.0.0.53:53: read udp 192.168.1.11:36261->45.90.28.108:53: i/o timeout
  Traceroute error: lookup ipv4.dns1.nextdns.io on 127.0.0.53:53: read udp 192.168.1.11:47092->45.90.28.108:53: i/o timeout
  Traceroute error: lookup ipv4.dns2.nextdns.io on 127.0.0.53:53: read udp 192.168.1.11:45453->45.90.28.108:53: i/o timeout
Traceroute for anycast primary IPv4 (45.90.28.0)
    1    192.168.1.1    0ms   0ms   0ms
    2  96.120.26.245   15ms   9ms  14ms
    3 69.139.233.185   12ms  10ms   9ms
    4   68.85.177.29   11ms  10ms  11ms
    5 96.216.150.165   11ms   7ms   8ms
    6 96.216.150.162   16ms   7ms   9ms
    7  68.85.176.109   19ms  12ms  16ms
    8                   *     *     *
    9 200.189.230.70  142ms 144ms 139ms
   10  8.243.155.210  148ms 146ms 159ms
   11     45.90.28.0  141ms 144ms 140ms
Traceroute for anycast secondary IPv4 (45.90.30.0)
    1    192.168.1.1    0ms   0ms   0ms
    2  96.120.26.245   14ms   7ms  10ms
    3 69.139.233.185   13ms   9ms   8ms
    4   68.85.177.29   18ms  13ms  11ms
    5 96.216.150.165    9ms   8ms   7ms
    6   68.85.176.13   23ms  14ms  12ms
    7   96.110.40.49    *     *    16ms
    8  96.110.33.194   12ms  23ms  13ms
    9   62.115.54.21   12ms  14ms  12ms
   10                   *     *     *
   11  62.115.137.29   14ms  24ms  14ms
   12  209.170.76.34   21ms  15ms  15ms
   13     45.90.30.0   21ms  15ms  22ms
Do you want to send this report? [Y/n]: y
Optional email in case we need additional info: joe@inf7.net
Post unsuccessful: Post "https://api.nextdns.io/diagnostic": dial tcp: lookup api.nextdns.io on 127.0.0.53:53: read udp 192.168.1.11:58926->45.90.28.108:53: i/o timeout
Please report this issue on https://github.com/nextdns/diag
      • Eudes
      • 10 hrs ago
      • Reported - view

      try a traceroute to dns(dot)nextdns.io (Claro in Brazil is blocking it on their mobile network)-;

       

      if you try to switch to dns2(dot)nextdns(dot)io?

Login to reply

Content aside

  • 10 hrs agoLast active
  • 6Replies
  • 137Views
  • 5 Following