NextDNS outages - it is a daily routine now
NextDNS has been reliable, fast and really really great for me and my family - until January this year.
Something is not alright with the infra at NextDNS - daily outages both on UDP port 53 is now a common theme.
It first started with outages with DoT, and I reported the issue several times. Now the issue is affecting DoT, DoH and "normal" DNS over UDP.
This week, has been real bad. Forcing me to stop using it so I actually can work.
Please fix this, or atleast COMMUNICATE with your customers that is paying for the service. Provide us with tools that we can run periodically and submit reports with it.
My ISP is Telia, and I can confirm that other DNS-servers works - so it is not my connection that is borked.
I can't recommend nextdns to people or companies anymore, those who I recommended to use it last year have now switched back to google and cloudflare.
Here is the logs, the posting functionality does not even work...
╰─➤ sh -c 'sh -c "$(curl -s https://nextdns.io/diag)"'
Welcome to NextDNS network diagnostic tool.
This tool will download a small binary to capture latency and routing information
regarding the connectivity of your network with NextDNS. In order to perform a
traceroute, root permission is required. You may therefore be asked to provide
your password for sudo.
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 86.106.103.153:443: i/o timeout
Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp 188.172.192.71:443: connect: connection timed out
Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
edis-cph: 9.814ms
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: connect: connection timed out
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: connect: connection timed out
Pinging PoPs
edis-cph: 9.857ms
anexia-osl: 14.568ms
zepto-sto: 19.114ms
anexia-sto: 19.16ms
melbicom-rix: 28ms
edis-rix: 27.783ms
anexia-ams: 29.261ms
vultr-ams: 27.61ms
zepto-osl: 29.522ms
Traceroute for ultra low latency primary IPv4 (188.172.192.71)
1 192.168.2.254 0ms 0ms 0ms
2 81.235.16.1 1ms 0ms 0ms
3 81.228.91.100 7ms 7ms 7ms
4 81.228.89.188 8ms 7ms 7ms
5 81.228.84.95 7ms 8ms 8ms
6 62.115.123.158 8ms 8ms 8ms
7 62.115.159.210 8ms 8ms 8ms
8 94.16.22.32 8ms 8ms 8ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
Traceroute for ultra low latency secondary IPv4 (192.36.27.86)
1 192.168.2.254 0ms 0ms 0ms
2 81.235.16.1 1ms 1ms 1ms
3 81.228.91.100 8ms 7ms 7ms
4 81.228.89.188 7ms 7ms 7ms
5 81.228.84.95 7ms 7ms 7ms
6 62.115.123.158 8ms 8ms 8ms
7 62.115.143.6 9ms 12ms 12ms
8 62.115.134.81 9ms 9ms 9ms
9 213.248.89.119 9ms 9ms 9ms
10 * * *
11 * * *
12 192.36.27.86 9ms 9ms 9ms
Traceroute for anycast primary IPv4 (45.90.28.0)
1 192.168.2.254 0ms 0ms 0ms
2 81.235.16.1 1ms 0ms 0ms
3 81.228.91.100 7ms 8ms 8ms
4 81.228.89.188 7ms 7ms 7ms
5 81.228.84.95 7ms 8ms 8ms
6 62.115.123.158 8ms 8ms 8ms
7 62.115.143.6 21ms 22ms 20ms
8 62.115.134.79 17ms 17ms 17ms
9 62.115.118.107 17ms 17ms 17ms
10 62.115.163.50 18ms 18ms 18ms
11 212.103.51.241 18ms 18ms 18ms
12 45.11.107.151 18ms 18ms 18ms
13 45.90.28.0 18ms 18ms 18ms
Traceroute for anycast secondary IPv4 (45.90.30.0)
1 192.168.2.254 0ms 0ms 0ms
2 81.235.16.1 1ms 0ms 1ms
3 81.228.91.100 8ms 7ms 7ms
4 81.228.89.188 7ms 7ms 7ms
5 81.228.84.95 7ms 8ms 8ms
6 62.115.123.158 8ms 8ms 8ms
7 62.115.159.210 8ms 8ms 8ms
8 94.16.22.32 8ms 8ms 8ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
Do you want to send this report? [Y/n]: y
Optional email in case we need additional info: admin@domain.tld
Post unsuccessful: status 400
{"error":"0: instance.Test requires property \"Client\"\n"}#
18 replies
-
AS 3301
-
I am pretty convinced that the issue started when the web3 support was added into nextdns. Maybe some resolvers are overloaded....
However, I have now canceled my plan, after almost two years. Feels really sad but I feel that I have not choice.
-
Please share your IP in DM so we can investigate.
-
For the first time (ever) I had an outage yesterday, and then again just now. I've shared my IP address via DM.
-
So I had to disable "private DNS" on some android devices this morning, since they had this issue aswell.
-
Any news regarding this?
Is the NewDNS staff not able to answer here on this forum? Or is this forum only for users communicating with other users? -
I'm having the same problem. Sent the staff a DM with no response. Sent them another this morning as the problem is back again.
-
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...
-
Hi, I have the same problem since January. I have daily outage that last for a couple minutes, especially in the evenings (Past 4 p.m., CEST UTC/GMT +2 hours).
When it happens, the connection to the DNS-Server will first get slower and the latency will go up. Than there will be the outage and when the connection is restored, the latency will stay on a high level until the next day.:
https://nextdns.io/diag/40d1dd90-c323-11ec-8481-676889dfe9b3
Normally the latency should be down to around 10ms.
Thanks for your help in advance! -
Im geting alot of this lately at several locations and customers started compling,for example this location has good fibre connection 200/200mbit and its runing on Mikrotik router.I already contacted mikrotik with logs they told me nothing wrong their side, its nextdns servers that are having issues.
https://nextdns.io/diag/604b0860-c484-11ec-a469-09d937cbeb62
-
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
Content aside
-
4
Likes
- 2 yrs agoLast active
- 18Replies
- 1771Views
-
9
Following