1

Speed issues with NextDns

I have been facing speed issues while using Nextdns last few days.

I also checked Dnsperf where NextDns came 3rd in speed but last in terms of quality and uptime! Why is this happening? Is Nextdns closing down business or something? 

5 replies

null
    • Andreas_Schmid
    • 2 yrs ago
    • Reported - view

    I also see the same issues. I just signed up recently and everything seemed to be okay in the beginning but now I am getting frequent problems. Some times websites do not load or on-line meetings voice/video drops for a few seconds. It all points to the DNS not responding.

    When I switch back to ISP provided DNS the problems go away.

    I have also asked a question on the forum about name resolution and there was simply no answer at all. I am wondering to what's going on here. Service disruption and a support team that doesn't seem to respond at all doesn't look good ...

    • NextDNs
    • 2 yrs ago
    • Reported - view

    Please provide a https://nextdns.io/diag

    • Andreas_Schmid
    • 2 yrs ago
    • Reported - view

    Diag provided: https://nextdns.io/diag/cb269180-5c34-11ec-b1bb-a7e7db374e97

      • NextDNs
      • 2 yrs ago
      • Reported - view

      Andreas Schmid you have good routing and none of the locations you are routed too had any issues in the past few months and it does not look like your IP got block for any reason. Are you sure your issue is DNS related?

      • Andreas_Schmid
      • 2 yrs ago
      • Reported - view

      NextDNS I am sure it's DNS related but I also have been playing with the NextDNS CLI client as I wanted to get local client name resolution. I had consistent issues that for example one client got identified as "Macmini" correctly in a few second later as "Device #XXXXX". I don't know why this happened and have no resolution to this but there seems to be a few issues with the CLI client.

      So in the meantime I have taken this out of the equation and I am now forwarding DNS queries from my router and local AdGuard Home server directly to NextDNS. This seems to run okay at the moment. I think the CLI client was causing the previous issues.

      It would have been nice to be able to use the NextDNS CLI client (to get local hostnames in Next DNS) as I could then get rid of my AdGuard DNS server completely. I guess that tool still needs a bit of maturing so I am bridging this with a local AdGuard DNS to see what clients are doing and NextDNS to have overall control what is going out of my network. 

Login to reply

Content aside

  • 1 Likes
  • 2 yrs agoLast active
  • 5Replies
  • 320Views
  • 3 Following