2

NextDNS down

For last minutes, the whole DNS was done for me from Germany.

56replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • What do you get for https://ping.nextdns.io?

    Like 1
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 1 yr ago
      • Reported - view

      NextDNS 

        zepto-fra           12 ms

        vultr-fra           13 ms

        anexia-fra (IPv6)   13 ms  (anycast2, ultralow2)

        vultr-fra (IPv6)    13 ms

      ■ zepto-dus (IPv6)    14 ms  (anycast1, ultralow1)

        zepto-dus           14 ms  (anycast1, ultralow1)

        zepto-ams           15 ms

        vultr-ams (IPv6)    16 ms

        zepto-fra (IPv6)    16 ms

        anexia-fra          16 ms  (anycast2, ultralow2)

        anexia-cph          17 ms

        anexia-prg          19 ms

        anexia-ams (IPv6)   19 ms

        anexia-ams          19 ms

        anexia-cph (IPv6)   20 ms

        anexia-prg (IPv6)   23 ms

        vultr-ams           25 ms

        estnoc-cph          29 ms

      Like
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 1 yr ago
      • Reported - view

      DynamicNotSlow from mobile phone with mobile network I get:

       

        vultr-fra 25 ms (ultralow2)

        vultr-fra (IPv6) 31 ms (ultralow2)

        zepto-fra 31 ms

        anexia-fra (IPv6) 33 ms (anycast2, ultralow1)

        zepto-dus (IPv6) 35 ms

        anexia-fra 36 ms (anycast2)

        zepto-dus 39 ms

        anexia-zrh 40 ms

        exoscale-zrh (IPv6) 41 ms

        exoscale-zrh 41 ms

      ■ zepto-fra (IPv6) 42 ms (anycast1)

        zepto-mil (IPv6) 42 ms

        zepto-bru 43 ms

        zepto-mil 43 ms

        zepto-bru (IPv6) 44 ms

        vultr-lon 47 ms (anycast1, ultralow1)

        anexia-zrh (IPv6) 48 ms

        fusa-bru 51 ms

        fusa-bru (IPv6) 57 ms

        serverwala-mil 64 ms

      Like
  • Looks ok. Are you still having issues?

    Like
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 1 yr ago
      • Reported - view

      NextDNS everything is fine

      Like
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 1 yr ago
      • Reported - view

      NextDNS problem is/ was sadly back.

      after i change DNS to Quad9, i download diag tool but i'm not sure if downtime was resolved before i run the tool:

      Posted: https://nextdns.io/diag/c40a7170-b3ea-11eb-9e2c-0f3dbd428c27

      Like
    • DynamicNotSlow from network point of view, it’s all good. Can you give us more info about what is happening?

      Like 1
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 1 yr ago
      • Reported - view

      NextDNS whole DNS isn't usable in my case then.

      Even nslookup to NextDNS server. Changing DNS fixes it immediately

      Like
    • DynamicNotSlow how did you setup NextDNS? Which protocol? Which platform?

      Like 1
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 1 yr ago
      • Reported - view

      NextDNS I use DoT in my Router (Fritzbox 7590) but with fallback to non encrypted NextDNS DNS.

      On Windows PC I doesn't change anything but use DoH in Edge (so I can use different NextDNS profiles).

      The nslookup commands isn't of course affected by configuration in Edge so that doesn't matter.

      Like
    • DynamicNotSlow when nslookup is broken, is Edge affected the same way?

      Like 1
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 1 yr ago
      • Reported - view

      NextDNS yes

      Like
    • DynamicNotSlow can you please try removing NextDNS from your router and see if Edge still get the issue? Note that if your router start failing resolution, Edge won't be able to connect to DoH, as it depends on the system's DNS to resolve "dns.nextdns.io". I suspect there is something funky with your router and DoT, so excluding your router from the equation would help locating the issue.

      Like 1
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 1 yr ago
      • Reported - view

      NextDNS makes sense.

      in all the months i have been using nextdns, i have only had this problem twice.

      I will leave the setup as it is for now and report any errors.

      Like
  • I have the same issue and I also live in Germany. Its quite frequent in the last 2-3 weeks. For a few minutes my devices can't resolve any domain and a few minutes later, after the cache expires, it starts working again.

    Like 1
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 1 yr ago
      • Reported - view

      Silas did you use a Fritzbox too?

      If so, how is your configuration?

      Like
      • Silas
      • Silas
      • 1 yr ago
      • 1
      • Reported - view

      DynamicNotSlow  Yes, I'm using the same configuration. But I enabled the fallback.

      Like 1
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 1 yr ago
      • Reported - view

      Silas so it doesn't help like it should.

      Thanks for feedback!

      Like
  • Having the Same issues as described above.  Living in Germany.

    Router is a Fritzbox 6660 configured with dot. Fallback enabled. 

    DNS resolving doesn't work 1-2 Times per hour, sometimes more often. 

    Extremely annoying.  The issue comes Up about 1-1,5 weeks ago. 

    Like 2
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 1 yr ago
      • 1
      • Reported - view

      Onslaught thanks for feedback

      Like 1
  • Same problem. This is driving me nuts. 

    For 2-5 minutes no webpage will open.

    https://nextdns.io/diag/8b2dc9b0-fdaf-11eb-8118-33e4ea455586

    Like
    • Kai Kaltenpoth do you have a fritzbox with nextdns configured as DoT?

      Like 1
    • NextDNS Yes. 

      Like 1
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 10 mths ago
      • Reported - view

      Kai Kaltenpoth it's known problem with FritzBox.

      Don't know if NextDNS can do anything but take a look at above comments.

      Currently i use Quad9 in FritzBox and NextDNS in browser which works without problems.

      Like
    • DynamicNotSlow Well then i have to cancel my nextdns plan. 

      Like
  • I have the same Problem in Germany now with Fritzbox 6591! I test other DoT DNS Servers, there is working! What Fritz Version you all have?! NextDNS can you please look into this? Quad9 works perfect with DoT! I want make a subscription 

    Like 1
  • Still no fix for that. Still the old problem. And nobody cares.

    Like
      • JCVR
      • jcvr
      • 5 mths ago
      • Reported - view

      Kai Kaltenpoth Yes, it works if you do not use DoT or DoH. But then you are stuck with unencrypted DNS. Since it seems that NextDNS does not even acknowledge this issue I have switched back to the "anti malware" version of 1.1.1.1 - too bad, NextDNS is a great idea!

      Like
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 5 mths ago
      • Reported - view

      JCVR I use Quad9 only in my router and also add my NextDNS accounts into the Name resolution Part. 

      On Windows11 I configure NextDNS in network Settings so the whole system use encrypted DNS while resolution always works now - thanks to Quad9 in router as „backend“

      Like
  • to the top!

    Like
  • I was wondering, why I sometimes have short DNS outages. It just does not resolve anything, but once you start to search for the problem, it already works again. So yeah, count me in, I've got the same problem with DoT on the FRITZ!Box (fallback is of course enabled).

    I'm using a FRITZ!Box 6590 Cable with FRITZ!OS 07.29.

    Maybe someone from @NextDNS should get in contact with the FRITZ!Box people, e.g. via Twitter https://twitter.com/avm_de. They have a great technical support and answer almost immediately.  

    Like 1
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 5 mths ago
      • Reported - view

      Markus Schneider i fix the problem with using Quad9 in Fritz!Box DNS settings and NextDNS in Windows11.

       

      Using NextDNS in Fritz!Box (even with non encrypted fallback) doesn't work for my FritzBox 7590.

      Like
      • JCVR
      • jcvr
      • 5 mths ago
      • Reported - view

      Markus Schneider this issue is not fritzbox related. it is true for all DoT connections. unfortunately no solution for that yet

      Like
      • JCVR
      • jcvr
      • 5 mths ago
      • 1
      • Reported - view

      DynamicNotSlow any other dot service does work fine in fritzbox according to my tests.

      Like 1
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 5 mths ago
      • Reported - view

      JCVR thx for your feedback. Good to know!

      Like
    • JCVR DOT was broken on my iPhone and iPad this morning. I had switched them to DoT about 2 days ago.  This morning I was able to ping the NextDNS servers but resolution wouldn’t work.  Switched over to Cloudflare DoT on the phone for now. Waiting to see if the iPad recovers at some point. It might be unrelated to the Fritz Box issues but seems oddly similar.

      Like
    • JCVR Thanks for your feedback!

      Like
  • For everyone in this thread with recurrent DoT issues, could you please return the result of https://test.nextdns.io and provide your country/ISP if possible? Thanks.

    Like 1
    • NextDNS Germany, Vodafone Cable

      {
      "status": "ok",
      "protocol": "DOH",
      "profile": "*********",
      "client": "188.192.214.126",
      "srcIP": "188.192.214.126",
      "destIP": "116.203.147.209",
      "anycast": false,
      "server": "hetzner-nue-1",
      "clientName": "nextdns-mac",
      "deviceName": "*********",
      "deviceID": "*********",
      "deviceModel": "Apple MacBookPro17,1"
      }
      Like
      • Koboldchen
      • Koboldchen
      • 5 mths ago
      • Reported - view

      NextDNS Germany, 1&1

      {
          "status": "ok",
          "protocol": "DOT",
          "profile": "fpa530476ddf749cc7",
          "client": "2001:9e8:270c:cc00:742e:3dae:781f:6b6c",
          "srcIP": "2001:9e8:270c:cc00:742e:3dae:781f:6b6c",
          "anycast": false,
          "server": "anexia-fra-1",
          "clientName": "unknown-dot",
          "deviceName": "Kevin",
          "deviceID": "A3M3R"
      }

      Like
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 5 mths ago
      • Reported - view

      NextDNS Germany, Telekom („Mobilcom Debitel“ third Party Provider) with Apple PrivateRelay enabled and NextDNS Apple profile installed:

      {
      "status": "unconfigured",
      "resolver": "162.158.83.240",
      "ecs": "127.0.0.0/24/0",
      "srcIP": "2606:54c0:1e00:108::47:327",
      "server": "anexia-fra-1"
      }

       Without PrivateRelay:

      {
      "status": "ok",
      "protocol": "DOH",
      "profile": "XXXXXXX",
      "client": "80.187.114.12",
      "srcIP": "2a01:598:a051:652e:c005:e311:f038:1b8d",
      "destIP": "45.90.28.0",
      "anycast": true,
      "server": "zepto-fra-1",
      "clientName": "apple-profile"
      }
      Like
    • NextDNS Germany, Deutsche Telekom

      {
      "status": "ok",
      "protocol": "DOT",
      "profile": "xxxxxx",
      "client": "2003:f0:5fff:3cdb:464e:6dff:fe68:2c56",
      "srcIP": "2003:f0:5f3c:c200:5426:5f90:27c3:5f69",
      "anycast": false,
      "server": "hetzner-nue-1",
      "clientName": "unknown-dot"
      }
      Like
    • NextDNS 

      Germany, Telekom, t-online.de

      {
      "status": "ok",
      "protocol": "DOT",
      "profile": "fpd783371f7c25555c",
      "client": "87.157.87.101",
      "srcIP": "87.157.87.101",
      "destIP": "199.247.16.158",
      "anycast": false,
      "server": "vultr-fra-1",
      "clientName": "unknown-dot"
      }
      
      with ipv6 enabled
      
      {
      "status": "ok",
      "protocol": "DOT",
      "profile": "fpd783371f7c25555c",
      "client": "87.157.87.101",
      "srcIP": "2003:c2:5f0a:6a00:c2:cd99:cbbe:efd8",
      "destIP": "199.247.16.158",
      "anycast": false,
      "server": "vultr-fra-1",
      "clientName": "unknown-dot"
      }
      
      Like
    • NextDNS 

      {
      "status": "ok",
      "protocol": "DOT",
      "profile": "fp76a9fc8d89591bc9",
      "client": "92.201.200.36",
      "srcIP": "92.201.200.36",
      "destIP": "199.247.16.158",
      "anycast": false,
      "server": "vultr-fra-1",
      "clientName": "unknown-dot",
      "deviceName": "FritzBox",
      "deviceID": "7KFKC"
      }
      Like
    • NextDNS The same problem still occurs to me.

      My ISP is Korea/LG U+

      {
      "status": "ok",
      "protocol": "DOH",
      "profile": "fp51611629a2d39be9",
      "client": "180.226.212.17",
      "srcIP": "180.226.212.17",
      "destIP": "103.127.124.46",
      "anycast": false,
      "server": "zepto-sel-1",
      "clientName": "nextdns-cli",
      "deviceName": "VELVET",
      "deviceID": "1992V",
      "deviceIP": "192.168.1.105",
      "deviceModel": "mac:a0:4f:85"
      }
      Like
  • Usa IL metro pcs 

    {
    "status": "ok",
    "protocol": "DOT",
    "profile": "fp581ba960ae56e051",
    "client": "2607:fb90:e1f1:bcd3:0:a:db2d:8f01",
    "srcIP": "2607:fb90:e1f1:bcd3:0:a:db2d:8f01",
    "anycast": false,
    "server": "vultr-chi-1",
    "clientName": "unknown-dot"
    }
    Like
  • Same problem for me. NetCologne, Germany with a FRITZ!Box 7590 AX.

    Like
  • Same Problem with my Fritz!Box Cable 6690 with Vodafone Cable in Germany

    Like
  • Rise to the top. Still not working. No status update from @nextdns

    Like
      • JCVR
      • jcvr
      • 4 mths ago
      • 1
      • Reported - view

      Kai Kaltenpoth there was a fix applied yesterday that caused me not to notice outages for 5 hours. however the fix caused other issues and had to be rolled back. there soon will be a final fix i guess.

      Like 1
  • We just rolled out a fix for this issue in Germany's PoPs. Please test and tell us if you can confirm it is resolved.

    Like 4
      • JCVR
      • jcvr
      • 4 mths ago
      • 2
      • Reported - view

      NextDNS I have tested for about 10 hours now and no issues yet. Compared to before where I could reproduce the issue very quickly this is a vast improvement. I will keep on testing just to be sure.

      Like 2
    • JCVR thanks for your help on this.

      Like 1
      • J. E.
      • J_E
      • 4 mths ago
      • 2
      • Reported - view

      NextDNS it seems to work perfectly. we've been testing it for 6 hours and haven't had any problems yet. thank you!

      Like 2
  • I just posted a few minutes ago about this exact problem: Intermittent DNS resolution issues - Discussions - NextDNS Help Center and then saw this threat.

    If this is resolved now would be great!

    Like
    • Andreas Schmid Yeah, works right now and would be great if it stays that way. I already was planing to cancel my subscription, as these intermittent problems really got on my nerves 🙄 

      Like
Like2 Follow
  • Status Fixed
  • 2 Likes
  • 3 mths agoLast active
  • 56Replies
  • 1571Views
  • 17 Following