0

NextDNS down

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

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

    Like
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 1 mth 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 mth 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 mth ago
      • Reported - view

      NextDNS everything is fine

      Like
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 1 mth 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 mth 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 mth 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 mth 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 mth 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 mth ago
      • Reported - view

      Silas did you use a Fritzbox too?

      If so, how is your configuration?

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

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

      Like 1
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 1 mth 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 1
      • DynamicNotSlow
      • Pro subscriber ✓
      • DynamicNotSlow
      • 1 mth ago
      • 1
      • Reported - view

      Onslaught thanks for feedback

      Like 1
Like Follow
  • 1 mth agoLast active
  • 20Replies
  • 245Views
  • 4 Following