1

Increase in Latency

Something has recently happened that is causing NextDNS to resolve a lot slower than it used to.
Previously it was closer to Cloudflare or Google's latency of sub-10ms, but now it's over 20 and sometimes 40ms.
Currently using ASUS-Merlin with DoT, works fine except resolving is a lot slower... any ideas?

11replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • For easier viewing since png previews aren't supported 

    Like
  • Looks like for some reason my East Coast resolver has been moved from Atlanta to Dallas... is there something wrong with the Atlanta server? Previously I was resolved to vultr-atl, but now resolving to vultr-dal... thanks!

    Like
  • I've definitely been  noticing this.  My pc is insanely fast to the point that normally web browsing appears instant, but lately the dns resolution time has been slowing down, impacting this.  

    (Or you can use DNS Benchmark - steve gibson to see the same thing objectively)

    You probably want to use that over a ping test, since  pinging isnt truly measuring query response latency.  

    Like
  • NextDNS steering just doesn’t work if you are using a device they don’t support. I had this same issue on my ASUS router. 
     

    I am in Qatar so should be connecting to sub 30 ms servers in the UAE and Saudi Arabia yet their steering was sending me to Australia which is >300 ms!

    This was not just affecting the resolving time, it was also resolving to very distant CDN endpoints on suboptimal routes causing incredibly slow speeds connecting to iCloud for example. I was getting sub 1 Mbps on my 1 Gbps connection! 
     

    What I ended up doing is making a list of nearby servers by resolving NextDNS server hostnames on ping.nextdns.io and used their IPs in the DoT setup field instead of the AnyCast IP NextDNS shows on the setup page.

    My fix is definitely not something I would recommend if you don’t like troubleshooting every now and then. I say this because if they ever change the servers and these IPs are not longer functional you’ll have to collect the new ones. I’ve been using this setup for a few months now though and so far no issues. 

    Like
  • I setup Technitium to act as a caching proxy infront of next dns (and it can be configured to use most of the blocklists nextdns does), way faster now. https://technitium.com/dns/

    Also checked my dns suffix list to make sure it wasnt sending multiple dns queries out.  

    Like
  • Posting this update here as users in Dallas are reporting an increase in latency as well... East Coast and still resolving to Dallas instead of Atlanta... 

    Like
  • Noticing significant lag recently as well in the Seattle area. 

    Like
  • Please open individual threads for each issue with a https://nextdns.io/diag

    Like
      • BS
      • teal_rabbit
      • 3 wk ago
      • Reported - view

      NextDNS Apologies if this seems dismissive, but shouldn't a simple PING along with the PING NextDNS URL also illustrate this issue as well? I'm currently running a NextDNS diagnostics for you, but I don't trust it's capabilities because it's already failed to detect IPv6 when I have a valid IPv6 address.

      Attached for your review. Thank you for your assistance and business. 

      https://nextdns.io/diag/09f6db60-92f1-11ed-b0e4-7b327fb22a8b

      Like
    • BS we are looking into it. Ping can show latency but is not helpful for debugging routing issues. The diag IPv6 detection seems broken indeed, we will fix it. It’s not because one feature of a tool is broken that it is all broken :)

      Like 1
      • BS
      • teal_rabbit
      • 13 days ago
      • Reported - view

      NextDNS Update: Did a quick test via the ping utility, and I'm back on the East Coast and no longer in Texas. Thank you! 

      Like
Like1 Follow
  • 1 Likes
  • 13 days agoLast active
  • 11Replies
  • 278Views
  • 5 Following