1

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.

8 replies

null
    • William.13
    • 2 days ago
    • Reported - view

    Any updates on this? It's been nearly two weeks and the issue is persisting for me.

    • BigDargon
    • 2 days ago
    • Reported - view

    You need to post the resulting URL after running the diag tool. Otherwise, NextDNS developers won't know how to troubleshoot your network issues.

      • William.13
      • 2 days ago
      • Reported - view

      The diag tool does not work for me. I created an issue in the repo here for it: https://github.com/nextdns/diag/issues/35

      • BigDargon
      • yesterday
      • Reported - view

       The developer has responded to you on GitHub, please follow the instructions to report the bug.

    • stargolem
    • yesterday
    • Reported - view

    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.

    • William.13
    • yesterday
    • Reported - view

    Alright I've managed to get the diag tool working.

    Here is the report: https://nextdns.io/diag/fc094af0-220e-11f1-80fb-23f43a31b724

      • NextDNs
      • 20 hrs ago
      • Reported - view

      the one 91ms latency on the first hop (assuming your router) is suspicious. Are you sure you LAN is healthy?

      • William.13
      • 20 hrs ago
      • Reported - view

       I haven't noticed any issues with my LAN. High connectivity, no real problems from what I can tell.

      When I switched to Cloudfare's DNS servers, all of the issues were resolved. So I would imagine that if it were an issue with my LAN, it wouldn't have fixed itself after doing so.

Content aside

  • 1 Votes
  • 20 hrs agoLast active
  • 8Replies
  • 134Views
  • 4 Following