1

NextDNS periodically goes down for me (Dallas/Spectrum)

About once a day, NextDNS goes down for me, and I’m unable to connect to websites or the like. Typically, if I reboot my cable modem and router, that will usually fix things. (My issue sounds very similar to the issue that’s described here.)

The most recent time that this happened, which was about an hour ago, I followed the directions from the “Report network latency issue” page, and here are my results from my macOS 10.14 Mojave machine:

$ 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)
Password:
Resolvers:  192.168.7.1
Testing IPv6 connectivity

  available: false
Fetching https://test.nextdns.io
  Fetch error: Get "https://test.nextdns.io": dial tcp: lookup test.nextdns.io on 192.168.7.1:53: read udp 192.168.7.200:64225->192.168.7.1:53: read: connection refused
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 192.168.7.1:53: read udp 192.168.7.200:61442->192.168.7.1: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 192.168.7.1:53: read udp 192.168.7.200:65340->192.168.7.1:53: i/o timeout
Fetching PoP name for anycast primary IPv4 (45.90.28.0)
  vultr-dal: 16.729ms
Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
  anexia-dal: 16.689ms
Pinging PoPs
  error: Get "https://router.nextdns.io/?limit=10&stack=dual": dial tcp: lookup router.nextdns.io on 192.168.7.1:53: read udp 192.168.7.200:58746->192.168.7.1:53: i/o timeout
  Traceroute error: lookup ipv4.dns1.nextdns.io on 192.168.7.1:53: read udp 192.168.7.200:64770->192.168.7.1:53: read: connection refused
  Traceroute error: lookup ipv4.dns2.nextdns.io on 192.168.7.1:53: read udp 192.168.7.200:63073->192.168.7.1:53: i/o timeout
Traceroute for anycast primary IPv4 (45.90.28.0)
    1                   *     *     *
  error: cannot write ICMP packet: write ip 0.0.0.0->45.90.28.0: sendmsg: no route to host
Traceroute for anycast secondary IPv4 (45.90.30.0)
  error: cannot write ICMP packet: write ip 0.0.0.0->45.90.30.0: sendmsg: no route to host
Do you want to send this report? [Y/n]: Optional email in case we need additional info: Y
Post unsuccessful: status 400
{"error":"0: instance.Test requires property \"Client\"\n1: instance requires property \"SecondaryTraceroute\"\n"}

 

My ip address is 70.122.129.34, my router is an Eero, and my ISP is Spectrum. And if there might be any other information that you may need, I’d be happy to provide it. 

10 replies

null
    • Jonathan_Selea
    • 2 yrs ago
    • Reported - view

    Can confirm, that this issue is ingoing and has been also affecting me since january..

      • handcoding
      • 2 yrs ago
      • Reported - view

      Jonathan Sélea Have you by chance found any workarounds? With the way things have been going, I’m not sure how much longer I can keep using NextDNS.

      • Jonathan_Selea
      • 2 yrs ago
      • Reported - view

      Ashley Bischoff 

      I have not found any workaround, except the one that does not involve nextdns at all.

      I just posted my third topic regarding this, but I dont expect any real responses from nextdns sadly..

      • handcoding
      • 2 yrs ago
      • Reported - view

      Jonathan Sélea Fair enough.

    • handcoding
    • 2 yrs ago
    • Reported - view

    @nextdns I just noticed this happening again, so I thought that I’d provide some additional info—

    When I went to https://test.nextdns.io on my MacBook Pro (running macOS 10.14.6), here’s what I got:

    {
    "status": "ok",
    "protocol": "UDP",
    "profile": "fp3183f763d1d8e3a8",
    "client": "2603:8080:6d00:25f6:31fc:3e9d:980c:cd2c",
    "srcIP": "2603:8080:6d00:25f6:31fc:3e9d:980c:cd2c",
    "anycast": true,
    "server": "vultr-dal-1",
    "clientName": "unknown"
    }

    I also tried to load ping.nextdns.io, but it wouldn’t load for me. (image attached).

    Lastly, I also tried running the diagnostic tool, but it quit early after the “press enter to accept” part:

    $ 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)
    
    $
      • handcoding
      • 2 yrs ago
      • Reported - view

      nextdns Just for completeness—and if it may help at all—here’s what I get from https://test.nextdns.io when my connection from my MacBook Pro to NextDNS is in a working state:

      {
      "status": "ok",
      "protocol": "DOH",
      "profile": "fp725fe9845d83beb2",
      "client": "70.122.129.34",
      "srcIP": "2603:8080:6d00:25f6:d4fe:d159:93bd:3ab5",
      "destIP": "188.172.251.1",
      "anycast": false,
      "server": "anexia-dal-1",
      "clientName": "nextdns-mac",
      "deviceName": "Ashley’s MacBook Pro",
      "deviceID": "WPRWF",
      "deviceModel": "Apple MacBookPro11,5"
      }
    • handcoding
    • 2 yrs ago
    • Reported - view

    @nextdns I’m not sure if this might be an additional data point, but I just noticed on my.nextdns.io that one of my configuration profiles says to configure my router to use these IPV4 DNS servers:

    45.90.28.74 and 45.90.30.74

    While my other configuration profile says to configure my router to use these IPV4 DNS servers:

    45.90.28.248 and 45.90.30.248

    Can I ask which one of those is correct? 

      • losnad
      • 2 yrs ago
      • Reported - view

      Every new configuration get random X Ip's, one in 45.90.28.X and one 45.90.30.X. This ones are shared between all users and need linked IP. The IPv6 one are individual. Better to use DoH or DoT.

      You use which configuration want.

      • handcoding
      • 2 yrs ago
      • Reported - view

      losnad Ohhh—that’s helpful info! 

      And for better or for worse, my Eero router won’t let me configure only IPV6 DNS servers—I have to configure both IPV4 and IPV6. So I’ve entered both IPV4 and IPV6 on my Eero, and thanks again for the info about the IPV4 servers.

    • kevin_v
    • 2 yrs ago
    • Reported - view

    Same Problem with Spectrum in Tampa.  Something overnight happens with Spectrum / NextDNS / EERO combination.  Just turned off NextDNS got tired of daily resetting the network. 

Content aside

  • 1 Likes
  • 2 yrs agoLast active
  • 10Replies
  • 500Views
  • 3 Following