2

NextDNS down

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

51 replies

null
    • Stormchaser1901
    • 3 yrs ago
    • Reported - view

    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 

    • Kai_Kaltenpoth
    • 3 yrs ago
    • Reported - view

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

      • Pro subscriber ✓
      • DynamicNotSlow
      • 3 yrs 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“

    • Kai_Kaltenpoth
    • 3 yrs ago
    • Reported - view

    to the top!

    • Markus_Schneider
    • 3 yrs ago
    • Reported - view

    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.  

      • Pro subscriber ✓
      • DynamicNotSlow
      • 3 yrs 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.

      • Pro subscriber ✓
      • DynamicNotSlow
      • 3 yrs ago
      • Reported - view

      JCVR thx for your feedback. Good to know!

      • Chris_Leidich
      • 3 yrs ago
      • Reported - view

      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.

      • Markus_Schneider
      • 3 yrs ago
      • Reported - view

      JCVR Thanks for your feedback!

    • NextDNs
    • 3 yrs ago
    • Reported - view

    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.

      • Markus_Schneider
      • 3 yrs ago
      • Reported - view

      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"
}
      • Koboldchen
      • 3 yrs 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"
      }

      • Pro subscriber ✓
      • DynamicNotSlow
      • 3 yrs 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"
}
      • Rudiger_Erdmann
      • 3 yrs ago
      • Reported - view

      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"
}
      • Kai_Kaltenpoth
      • 3 yrs ago
      • Reported - view

      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"
}
      • ChristianHouben
      • 3 yrs ago
      • Reported - view

      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"
}
      • YunSung_Hwang
      • 3 yrs ago
      • Reported - view

      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"
}
    • ray_toth
    • 3 yrs ago
    • Reported - view

    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"
}
    • stfn
    • 3 yrs ago
    • Reported - view

    Same problem for me. NetCologne, Germany with a FRITZ!Box 7590 AX.

    • J_E
    • 3 yrs ago
    • Reported - view

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

    • Kai_Kaltenpoth
    • 3 yrs ago
    • Reported - view

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

    • NextDNs
    • 3 yrs ago
    • Reported - view

    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.

      • NextDNs
      • 3 yrs ago
      • Reported - view

      JCVR thanks for your help on this.

      • J_E
      • 3 yrs ago
      • 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!

    • Andreas_Schmid
    • 3 yrs ago
    • Reported - view

    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!

Login to reply

Content aside

  • Status Fixed
  • 2 Votes
  • 3 yrs agoLast active
  • 51Replies
  • 2334Views
  • 15 Following