Internet Dropout Daily
Since I switched to paid NextDNS I am getting internet droputs at least once a day around 10am-11am MST. The dropouts last for about 1-2 minutes and effect both wifi and ethernet connections simultaneously. I have NextDNS setup at router level and not individual devices. It takes down internet for all devices in home for both wifi and ethernet connections. Is there some kind of NextDNS maintenance schedule going on during this time every day? Is there a solution? Why didn't this happen when I was using the free version? Any help or advice is appreciated.
-
I am suffering with the same issues - it started with once a day, but now we experience this multiple times every day.
dial tcp: lookup ipv4.dns2.nextdns.io on 10.69.69.1:53: read udp 10.69.69.17:50174->45.90.28.24:53: i/o timeout
Fetching PoP name for anycast primary IPv4 (45.90.28.0)-
Lana Jaeger stop posting your nonsense spam
-
-
Also having this issue. I only was able to determine it as my work laptop has a different DNS
-
Same here. Can't even ping any NextDNS IP's from my static Public IP. But i am able to when I change my Public IP. It's as if NextDNS is blocking all comms from a specific IP for some reason and then after a few hours allows it again
-
Jaco Marais please provide the problematic IP in DM so we can investigate
-
NextDNS good day. I've sent a DM with the info as requested. The problem has returned today after being absent for about a month. Currently I'm not able to ping the DNS IP from that specific public IP
-
Jaco Marais test results from ping.nextdns.io
web4africa-nbo 78 ms
garanntor-los 188 ms
citynet-cai 238 ms
navico-ruh 252 ms
premiumrdp-ruh 275 ms
edis-dxb 300 ms
anexia-dxb 316 ms
zepto-jnb error
anexia-jnb error
do-blr error
anycast.dns1.nextdns.io error (anycast1)
anycast.dns2.nextdns.io error (anycast2)
dns1.nextdns.io error (ultralow1)
dns2.nextdns.io error (ultralow2)
-
-
Follow up as it is happening again right now. I have a custom config setup through pfsense with both my DNS resolver set accordingly and dynamic DNS set on NextDNS. Any sort of DNS resolution gets no response from IPv4 or 6. This is the third day in a row
-
Michael Campbell can you please DM your IP?
-
-
Same issue here, am getting NXDOMAIN responses for common sites and this does appear to be happening throughout the day for me and seems to be getting more frequent. This has only occurred during the last week - since we completely lost connectivity due to a DoT change that was rolled back.
-
Just an update:
Every device in our network that uses DoT/DoH continues to have this issues daily, while "normal" DNS works fine.
These issues last between 10-30 minutes each time, and I am not always capable of running troubleshooting-tests from my PC every time it occurs.
Is there any tool that NextDNS can provide that automatically can monitor the connection, and report outages? I would gladly run that 24/7 if that can help NextDNS find this very real issue that affect this service that I pay for - but can't use reliably anymore. -
The problem is back (started 20 min ago).
No response or reply from NextDNS on any of my DM's for the last few months.
This is very very bad customer service, and I'm a paying customer...
-
Jaco Marais can you please provide a https://nextdns.io/diag
-
-
Hi, I've been having the same issue for more than 3 weeks now since it started to become more obvious. I had no choice but to switch to a different DNS address for now since my connection keeps dropping every couple of minutes, surfing is horribly slow and it is just unusable.
P.s. I had to use a different dns in order to access https://ping.nextdns.io kindly refer to the attached screenshot-
Ken Abadilla please provide a https://nextdns.io/diag
-
NextDNS Hello, hello. Can you pair your DNS service with the Adguard app? Or is it necessary to prescribe everything separately and not combine them together?
-
-
Hi guys,
I'm using a paid account. We have the same outage since around 2 weeks, always 2-3 times a day between 12-14 MEST. Additionaly, there was no outage over the weekend. Maybe it's a weekday ghost :)
I used the diag tool and sent the report. Here is the excerpt.
Welcome to NextDNS network diagnostic tool.
This tool will capture latency and routing information regarding
the connectivity of your network with NextDNS.
The source code of this tool is available at https://github.com/nextdns/diag
Do you want to continue? (press enter to accept)
Testing IPv6 connectivity
available: false
Fetching https://test.nextdns.io
Fetch error: Get "https://test.nextdns.io": dial tcp: lookup test.nextdns.io: no such host
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: no such host
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: no such host
Fetching PoP name for anycast primary IPv4 (45.90.28.0)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp 45.90.28.0:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp 45.90.30.0:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Pinging PoPs
error: Get "https://router.nextdns.io/?limit=10&stack=dual": dial tcp: lookup router.nextdns.io: no such host
Traceroute error: lookup ipv4.dns1.nextdns.io: no such host
Traceroute error: lookup ipv4.dns2.nextdns.io: no such host
Traceroute for anycast primary IPv4 (45.90.28.0)
1 192.168.1.1 4ms 4ms 4ms
2 62.155.243.201 9ms 9ms 9ms
3 217.0.194.154 14ms 15ms 13ms
4 217.0.194.154 14ms 15ms 14ms
5 80.157.128.214 15ms 16ms 14ms
6 80.255.9.62 12ms 15ms 15ms
7 156.146.32.41 19ms 15ms 14ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Traceroute for anycast secondary IPv4 (45.90.30.0)
1 192.168.1.1 5ms 4ms 4ms
2 62.155.243.201 10ms 12ms 8ms
3 217.0.192.190 14ms 13ms 14ms
4 217.0.192.190 15ms 13ms 13ms
5 213.248.93.186 14ms 13ms 13ms
6 62.115.14.117 15ms 15ms 14ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
-
Dr. Heiko Tobias
You did not get a reply from the nextdns team right?
-
-
And here we go again. NO REPOSE FROM NEXTDNS DNS SERVERS (and also the NextDNS staff, go figure).
DNS has been down since 06h10 this morning. It's now 08h10.
Running on Quad9 once again until NextDNS or the staff wakes up
-
Jaco Marais please provide a https://nextdns.io/diag
-
NextDNS i provided one above with no feedback. The problem resolved again after a few hours so Im not able to provide a new correct diagnostic report unfortunately.
-
Jaco Marais I can’t find a diag from you in this thread. We also need a recent one in order to investigate.
-
NextDNS i have just run another Diag. I'm not experiencing any issue at the moment, but I hope it helps:
https://nextdns.io/diag/d56f3e60-e6fb-11ec-a234-1df5ce60521f
-
