Inconsistent, high DNS latency
I've been experiencing sporadic high latencies with DNS lookups using NextDNS over the last few days. This is manifesting as apps sometimes mistakingly thinking that I am not connected to the internet, long buffer times, and overall poor network performance.
I can verify the issue by running a time nslookup command while using the NextDNS servers, and seeing lookups of 10 seconds or longer. Not every lookup takes this long, but many do. Here is an example looking up google.com:
time nslookup google.com
Server: 45.90.30.193
Address: 45.90.30.193#53
Non-authoritative answer:
Name: google.com
Address: 142.251.32.14
nslookup google.com 0.00s user 0.01s system 0% cpu 13.082 total
And another looking up slack.com:
time nslookup slack.com
Server: 45.90.30.193
Address: 45.90.30.193#53
Non-authoritative answer:
Name: slack.com
Address: 3.143.19.65
Name: slack.com
Address: 3.143.53.1
Name: slack.com
Address: 18.221.229.81
Name: slack.com
Address: 18.216.36.190
Name: slack.com
Address: 3.142.111.40
Name: slack.com
Address: 3.129.123.235
Name: slack.com
Address: 3.130.95.182
Name: slack.com
Address: 3.22.139.176
Name: slack.com
Address: 3.134.44.134
nslookup slack.com 0.00s user 0.02s system 0% cpu 13.093 total
Sometime the issue is so bad that the lookup fails entirely:
time nslookup google.com
;; connection timed out; no servers could be reached
nslookup google.com 0.00s user 0.02s system 0% cpu 18.052 total
When forcing another DNS host, such as 8.8.8.8, the issue is not apparent and I always get a response in less than a second:
time nslookup slack.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: slack.com
Address: 18.216.36.190
Name: slack.com
Address: 3.129.123.235
Name: slack.com
Address: 18.221.229.81
Name: slack.com
Address: 3.130.95.182
Name: slack.com
Address: 3.22.139.176
Name: slack.com
Address: 3.143.53.1
Name: slack.com
Address: 3.143.19.65
Name: slack.com
Address: 3.134.44.134
Name: slack.com
Address: 3.142.111.40
nslookup slack.com 8.8.8.8 0.00s user 0.02s system 27% cpu 0.070 total
I tried running the diagnostic tool, but I ran into another issue with the tool itself which prevented the report from being posted.
10 replies
-
Any updates on this? It's been nearly two weeks and the issue is persisting for me.
-
You need to post the resulting URL after running the diag tool. Otherwise, NextDNS developers won't know how to troubleshoot your network issues.
-
I have the same problem. For three or four weeks now there a such high latencies or even no resolves at all that machines/apps mistakingly thinking they are not connected to the internet. Quiet annoying situation.
-
Alright I've managed to get the diag tool working.
Here is the report: https://nextdns.io/diag/fc094af0-220e-11f1-80fb-23f43a31b724
-
There has not been much movement on this issue and I'm still experiencing problems. I just switched back to Cloudfare's DNS, and yet again, the DNS resolution latencies cleared up immediately.
I don't know how else to provide additional information for this issue. Based on someone else replying to this thread, I can tell I'm not alone. But NextDNS's position seems to be that there is no real problem and that it's an issue with the LAN. Which is pretty silly.
I'm going to be cancelling my subscription for the time being, and maybe at some point in the future, this issue will be resolved. I'll be switching to either a PiHole or just using my VPN provider's DNS blocker for the time being.
-
I've been having the same problem for a while as well. It's quite frustrating since it's definitely not on my end like the original poster. I can disable NextDNS and everything suddenly works fine. I've tried a different router as well with no change in results.
Testing IPv6 connectivity available: false Fetching https://test.nextdns.io Fetch error: Get "https://test.nextdns.io": EOF Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io) cloudzy-phx: 62.235ms Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io) anexia-lax: 12.45ms Fetching PoP name for anycast primary IPv4 (45.90.28.0) vultr-lax: 11.485ms Fetching PoP name for anycast secondary IPv4 (45.90.30.0) Fetch error: Get "https://dns.nextdns.io/info": EOF Pinging PoPs zepto-lax: 9.983ms vultr-lax: 10.626ms anexia-lax: 14.03ms zepto-sjc: 18.208ms bronto-slc: 24.772ms xmission-slc: 33.283ms smarthost-den: 40.354ms anexia-den: 42.227ms cloudzy-phx: 62.206ms vultr-sjc: 22.345ms Traceroute for ultra low latency primary IPv4 (172.86.65.4) 1 172.17.176.1 0ms 0ms 0ms 2 192.168.50.1 0ms 0ms 0ms 3 71.32.112.8 2ms 2ms 2ms 4 71.32.113.57 2ms 3ms 2ms 5 * * * 6 * * * 7 4.14.218.70 61ms 60ms 60ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 23.29.126.169 63ms 84ms 63ms 14 172.86.65.4 63ms 63ms 63ms Traceroute for ultra low latency secondary IPv4 (162.220.221.25) 1 172.17.176.1 0ms 0ms 0ms 2 192.168.50.1 0ms 0ms 0ms 3 71.32.112.8 2ms 4ms 2ms 4 71.32.113.57 5ms 4ms 2ms 5 * * * 6 4.69.219.218 4ms 3ms 3ms 7 129.250.8.90 3ms 3ms 2ms 8 * * * 9 129.250.3.131 13ms 12ms 12ms 10 128.242.179.2 12ms 12ms 12ms 11 188.172.215.32 20ms 13ms 12ms 12 162.220.221.25 12ms 13ms 13ms Traceroute for anycast primary IPv4 (45.90.28.0) 1 172.17.176.1 0ms 0ms 0ms 2 192.168.50.1 0ms 0ms 0ms 3 71.32.112.8 18ms 3ms 3ms 4 71.32.113.57 2ms 2ms 3ms 5 * * * 6 4.69.219.214 3ms 3ms 3ms 7 62.115.176.122 3ms 3ms 3ms 8 62.115.125.52 3ms 4ms 4ms 9 62.115.125.72 12ms 12ms 12ms 10 62.115.126.249 12ms * * 11 * * * 12 * * * 13 * * * 14 * * * 15 45.90.28.0 13ms 13ms 13ms Traceroute for anycast secondary IPv4 (45.90.30.0) 1 172.17.176.1 0ms 0ms 0ms 2 192.168.50.1 0ms 0ms 0ms 3 71.32.112.8 2ms 2ms 2ms 4 71.32.113.57 2ms 2ms 2ms 5 4.68.38.185 2ms 3ms 3ms 6 4.69.219.214 3ms 6ms 3ms 7 62.115.176.122 3ms 3ms 3ms 8 62.115.125.52 4ms 3ms 4ms 9 62.115.125.72 12ms 12ms 12ms 10 * * * 11 213.248.89.234 12ms 11ms 12ms 12 * * * 13 199.119.64.39 12ms 12ms 12ms 14 209.209.58.4 12ms 12ms 12ms 15 45.90.30.0 11ms 12ms 11ms
Content aside
-
1
Votes
- yesterdayLast active
- 10Replies
- 201Views
-
5
Following