0

Latency

Is this really where I should go for support? - I've used nextdns fine for 5 years. On Nov 4 my subscription expired and auto-renewed. Then I was entirely knocked off NextDNS, and was switched to DHCP for DNS. My credit card was charged. Then after about 4-5 hours, I was back on. Admittedly, during that time I was trying to get it setup. YogaDNS didn't work. Doing it by hand didn't work. Their app didn't work, then it did.

 

Subsequently, for 2 days my latency was HORRIBLE. Essentially, wherever I went on the web, there was a 5 or 6-second delay. I switched my DNS to quad9 and quit the nextdns app and, voilà, the delay was gone.

 

It is peculiar that my first real problem in 5 years came on the day my license renewed, however, I haven't been able to make it usable and am not sure where to go for support.

4 replies

null
    • Calvin_Hobbes
    • 2 wk ago
    • Reported - view

    I don’t have an answer for the problem you’re experiencing, but this is the official community support site.  The developers rarely answer support questions unfortunately, but there’s some really good and helpful community members here.

    There’s also a Subreddit r/nextdns and there are good members there too.   Some folks participate in both (I do).

    I don’t think your problem is related to the renewal, because DNS queries are still answered under the free plan, but the filtering stops working after 300k queries in a calendar month.     I’m guessing it was merely a coincidence that your problems occurred during renewal.   The problems were more likely due to you making configuration changes.   I’m not a windows or YogaDNS user, so really don’t have anything to offer for advice on how to fix what’s going on but wanted to let you know about the support options and how NextDNS works with and without a paid subscription.

    There’s a diagnostic utility you can find here https://help.nextdns.io/t/y4hmvcx/report-network-latency-issue. It creates a report that you can post and perhaps someone else can advise what to do next. It’s also possible there’s a routing problem between you and their servers, which would show up in the diagnostic report.

      • Steven_Shank
      • 2 wk ago
      • Reported - view

      Thank you. I sent the report.

       

      Here it is, if anyone can help with the issue.

      Testing IPv6 connectivity
        available: false
      Fetching https://test.nextdns.io
        status: unconfigured
        client: 73.164.251.8
        resolver: 66.185.115.249
      Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
        zepto-sea: 15.679ms
      Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
        zepto-sea: 19.107ms
      Fetching PoP name for anycast primary IPv4 (45.90.28.0)
        vultr-sea: 28.145ms
      Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
        zepto-sea: 17.688ms
      Pinging PoPs
        cacloud-yvr: 21.783ms
        vultr-sea: 21.793ms
        zepto-sea: 14.467ms
        anexia-yvr: 21.829ms
        tier-pdx: 29.41ms
        bronto-slc: 57.018ms
        zepto-sjc: 29.406ms
        xmission-slc: 36.369ms
        vultr-sjc: 27.897ms
        directspace-pdx: 30.033ms
      Traceroute for ultra low latency primary IPv4 (170.39.227.247)
          2  96.120.60.225   10ms  12ms  10ms
          3  68.87.219.121   11ms   9ms  10ms
          4  96.216.60.245   11ms  10ms  11ms
          5  68.85.243.197   31ms  11ms  13ms
          6    68.86.93.61   14ms  19ms  15ms
          7  96.110.34.142   14ms  14ms  16ms
          8                   *     *     *
          9                   *     *     *
         10   170.39.227.9   17ms  13ms  18ms
         11 170.39.227.247   17ms  15ms  20ms
      Traceroute for ultra low latency secondary IPv4 (170.39.227.247)
          2  96.120.60.225   11ms  10ms   9ms
          3  68.87.219.121   15ms  10ms  17ms
          4  96.216.60.245    9ms  10ms  10ms
          5  68.85.243.197   11ms  15ms  17ms
          6    68.86.93.61   14ms  15ms  14ms
          7  96.110.34.142   16ms  15ms  15ms
          8                   *     *     *
          9                   *     *     *
         10   170.39.227.9   14ms  13ms  14ms
         11 170.39.227.247   13ms  13ms  20ms
      Traceroute for anycast primary IPv4 (45.90.28.0)
          2  96.120.60.225   14ms  24ms  14ms
          3  68.87.219.121   15ms  24ms  16ms
          4  96.216.60.245   12ms  11ms  12ms
          5  68.85.243.197   11ms  11ms  10ms
          6    68.86.93.61   16ms  15ms  24ms
          7   96.110.44.94   15ms  16ms  14ms
          8 129.250.66.105   29ms  16ms  14ms
          9                   *     *     *
         10   129.250.2.99   15ms  14ms  16ms
         11 157.238.227.155   22ms  15ms  19ms
         12                   *     *     *
         13                   *     *     *
         14                   *     *     *
         15     45.90.28.0   30ms  14ms  14ms
      Traceroute for anycast secondary IPv4 (45.90.30.0)
          2  96.120.60.225   12ms   9ms  10ms
          3  68.87.219.121   15ms  11ms  11ms
          4  96.216.60.245   10ms   9ms   9ms
          5  68.85.243.197   18ms  17ms  11ms
          6    68.86.93.57   22ms  17ms  21ms
          7   96.110.44.90   17ms  18ms  18ms
          8 129.250.66.105   40ms  26ms  17ms
          9   129.250.2.94   20ms  17ms  15ms
         10  129.250.2.207   15ms  29ms  18ms
         11  128.241.15.50   13ms  16ms  16ms
         12                   *     *     *
         13   170.39.227.9   22ms  15ms  15ms
         14     45.90.30.0   15ms  13ms  15ms
      Do you want to send this report? [Y/n]: y
       

    • Steven_Shank
    • 12 days ago
    • Reported - view

    **Monday, Nov 11, 2024** - Followup. I used Quad9 for a week and then before switching to ControlD or Adguard I re-enabled NextDNS, now everything is fine. I have NO idea what the issue was, but there's no reason to switch as long as it is working well. Perhaps a DNS Cache issue? No idea.

      • Calvin_Hobbes
      • 12 days ago
      • Reported - view

      looks like there was a routing problem somewhere between your location and NextDNS 

Content aside

  • 12 days agoLast active
  • 4Replies
  • 88Views
  • 2 Following