0

NextDNS has stopped working

I'm paying for Premium, and it has been working for months, but recently NextDNS has stopped working. 

I have it set in my router, with the IP linked. Going to test.nextdns.io appears to show it configured. My machine, and other devices on my network, are correctly getting DNS from the router. Everything should be working, but it's not. If I test with AdGuardDNS, it works almost immediately, so I know my router's handling of custom DNS is working. So what do I do now? How do I get support?

17 replies

null
    • Rick_Mueller
    • 3 mths ago
    • Reported - view

    Actually, I'm wondering it it's IP related. I didn't pay too much attention, but the linked IP address might be wrong or old? Is there a way to purge them?

    • Rick_Mueller
    • 3 mths ago
    • Reported - view

    Anyone have any ideas? How do I get staff support for premium?

      • R_P_M
      • 3 mths ago
      • Reported - view

       If the linked IP is out of date/wrong there should be an option to update it in the settings page of NextDNS. I have been told (in the past) that it’s a recycle ♻️ type of icon next to the linked IP. 

      • Rick_Mueller
      • 3 mths ago
      • Reported - view

       I've linked the IP multiple times so I know it's correct. I also regularly call the link to sync it as well. 

      • R_P_M
      • 3 mths ago
      • Reported - view

      So is there a profile line being returned when you visit test.nextdns.io ?

      • Rick_Mueller
      • 3 mths ago
      • Reported - view

       The output it below. 

    • Rick_Mueller
    • 3 mths ago
    • Reported - view

    Here is the output from test.nextdns.io

     

    {
"status": "ok",
"protocol": "UDP",
"client": "172.56.73.242",
"srcIP": "172.56.75.24",
"destIP": "45.90.30.147",
"anycast": true,
"server": "anexia-mia-1",
"clientName": "unknown"
}
    • olearycrew
    • 3 mths ago
    • Reported - view

    I am having the exact same issue. DNS on my router is working correctly, my IP address is correct, test.nextdns.io shows what I'd expect...but NextDNS will not resolve any IP (just hangs when using the server directly through nslookup). This brings down "the internet" in my home because nothing can resolve DNS

      • olearycrew
      • 3 mths ago
      • Reported - view

      running the diag tool the only "error" i see is 

      Fetch error: Get "https://dns.nextdns.io/info": dial tcp 45.90.28.0:443: connect: operation timed out
    • Rick_Mueller
    • 3 mths ago
    • Reported - view

    Any advice here or ideas of how to get support?

    • Rick_Mueller
    • 3 mths ago
    • Reported - view

    So one thing I just noticed - If I open NextDNS for the first time in a day or two, my IP address that shows linked is x.x.x.24 - but my actual IP address is x.x.x.25 - when I link it, it changes, but doesn't work. So is there something wrong on the back end?

      • R_P_M
      • 3 mths ago
      • Reported - view

       This may be a problem with CGNAT as some ISPs use this to connect customers to the internet. NextDNS IP linking will not work with CGNAT (you would have to use the other protocols to get it working).

      Do you know if your ISP uses CGNAT at all? 

      • Rick_Mueller
      • 3 mths ago
      • Reported - view

       I don't believe so, I've been using it for a long time with no issues. 

    • TheAliDev
    • 3 mths ago
    • Reported - view

    Relink ip everytime your ip change

    If your router supports dynamic dns

    Then set it

      • Rick_Mueller
      • 3 mths ago
      • Reported - view

      I do relink it every time I move. It's still broken. 

    • Rick_Mueller
    • 3 mths ago
    • Reported - view

    I hate that I'm going to have to find different service and stop paying for this over lack of support. I knew it was a thing when I started paying for premium, but didn't know it would be nonexistent. 

      • R_P_M
      • 3 mths ago
      • Reported - view

       Try generating a new configuration profile and link your new IP there, see if that works. 
      For the output of test.nextdns.io you need a line labelled as “profile” for any blocking to be active. What you seem to be seeing is a “no profile” connection.

Login to reply

Content aside

  • 3 mths agoLast active
  • 17Replies
  • 565Views
  • 4 Following