0

my.nextdns.io is so slow or not working

Hi

My,nextdns.io has a very slow access many time for few past days. Take to 30 secs or more to show data.

Many times don't show data only circles moving only.

I need refresh browser many times to view any data.

 

Can you fix this?

 

Best.

3 replies

null
    • Lucasa
    • 3 wk ago
    • Reported - view

    I agree, NextDNS API is slow again and NextDNS is also having DNS redundancy issues.

    1) API has been repeatedly slow for several days!   

    2) Also, there must be a misconfiguration of routing to DNS servers in the East Coast to locate "USA servers"? 

     - For the 3rd day, we are seeing that NextDNS is ONLY using "1" DNS server. https://browserleaks.com/dns - 66.135.25.157    The Constant Company, LLC    United States, Piscataway.

     - Usually there are "2-3 or more USA DNS servers" that NextDNS uses to resolve queries.

    - In the past, this usually happens right before NextDNS services failover to overseas DNS servers in Australia, Russia, etc for queries. Not good!

    • BigDargon
    • 3 wk ago
    • Reported - view

    The domain my.nextdns.io uses Vercel's system, and the domain api.nextdns.io (for viewing logs) uses Cloudflare's system. Please check if your network routing to these services is stable?

    The API system from my network provider is accessing normally, only the routing service to Vercel is having errors. https://help.nextdns.io/t/p8yl98k/some-vercel-ip-addresses-are-not-responding-isp-viettel

      • Lucasa
      • 2 wk ago
      • Reported - view

       

      Thank you for the update: I cleared firewall/router (and workstation) DNS cache, rebooted and:

      1) Routing seems okay (below DIAG output); other than a few firewall hops in the traceroute of 66.135.25.157.

      2) Its the DNS resolution (DNS Leak Test) that keeps moving around (was stable at one time): seems like unstable DNS servers?

      DNS Leak Test

      Your IP Address
      IP Address    32.220.169.126
      ISP    Southern New England Telephone Company and SNET America
      Location    United States, New Haven
      Hide Your IP AddressDNS Leak Test
      Test Results    Found 2 Servers, 2 ISP, 2 Locations
      Your DNS Servers    
      IP Address :    ISP :    Location :
      86.106.90.57    M247 Europe SRL    United States, New York
      2a0e:6901:501:57:5054:ff:fe98:47ac    Misaka Network, Inc.    Canada, Montreal

      Your IP Address
      IP Address    32.220.169.126
      ISP    Southern New England Telephone Company and SNET America
      Location    United States, New Haven
      Hide Your IP AddressDNS Leak Test
      Test Results    Found 2 Servers, 1 ISP, 1 Location
      Your DNS Servers    
      IP Address :    ISP :    Location :
      66.135.25.157    The Constant Company, LLC    United States, Piscataway
      2001:19f0:c:a8e:3eec:efff:feb9:eede    The Constant Company, LLC    United States, Piscataway

      Your IP Address
      IP Address 32.220.169.126
      ISP Southern New England Telephone Company and SNET America
      Location United States, New Haven
      Hide Your IP AddressDNS Leak Test
      Test Results Found 10 Servers, 7 ISP, 6 Locations
      Your DNS Servers
      IP Address : ISP : Location :
      65.20.98.53 The Constant Company Spain, Madrid
      66.135.25.157 The Constant Company, LLC United States, Piscataway
      141.8.180.63 Yandex LLC Russia, Moscow
      162.220.223.23 ANEXIA Internetdienstleistungs GmbH United States, New York
      172.70.133.67 Cloudflare United States, Ashburn
      199.119.65.94 Misaka Network, Inc. United States, Dover
      208.69.32.141 Cisco OpenDNS, LLC United States, Ashburn
      2001:19f0:c:a8e:3eec:efff:feb9:eede The Constant Company, LLC United States, Piscataway
      2a00:11c0:46:4::5 ANEXIA Internetdienstleistungs GmbH United States, New York
      2a0b:4342:1a32:f:5054:ff:fe48:d17f Misaka Network, Inc. United States, Ashburn

       

      DIAG output:

      $ sh -c 'sh -c "$(curl -s https://nextdns.io/diag)"'

      Welcome to NextDNS network diagnostic tool.

      This tool will download a small binary to capture latency and routing information

      regarding the connectivity of your network with NextDNS. In order to perform a

      traceroute, root permission is required. You may therefore be asked to provide

      your password for sudo.

       

      The source code of this tool is available at https://github.com/nextdns/diag

       

      Do you want to continue? (press enter to accept)

      Password:

      Resolvers:  192.168.7.77

      Testing IPv6 connectivity

        available: false

      Fetching https://test.nextdns.io

        status: ok

        client: 32.220.169.126

        protocol: DOT

        dest IP: 45.90.28.102

        server: vultr-ewr-1

      Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)

        anexia-ewr: 6.999ms

      Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)

        vultr-ewr: 13.199ms

      Fetching PoP name for anycast primary IPv4 (45.90.28.0)

        vultr-ewr: 12.617ms

      Fetching PoP name for anycast secondary IPv4 (45.90.30.0)

        anexia-mnz: 58.987ms

      Pinging PoPs

        vultr-ewr: 8.048ms

        zepto-iad: 10.212ms

        zepto-xrs: 10.221ms

        anexia-ewr: 10.951ms

        hetzner-iad: 10.981ms

        teraswitch-pit: 14.261ms

        smarthost-bos: 16.552ms

        axcelx-bos: 17.404ms

        cloudzy-pit: 45.002ms

        anexia-mnz: 10.243ms

      Traceroute for ultra low latency primary IPv4 (162.220.223.23)

          1   192.168.7.77    0ms   0ms   0ms

          2   32.221.200.1    3ms   1ms   1ms

          3   172.76.21.25    2ms   2ms   2ms

          4  45.52.201.234    6ms   6ms   6ms

          5  74.41.143.173    6ms   5ms   5ms

          6     4.68.10.29   13ms  31ms   6ms

          7     4.68.75.78   45ms  16ms   6ms

          8  129.250.3.129    6ms   7ms   7ms

          9  129.250.3.213    7ms   8ms   7ms

         10 128.242.179.82    7ms   8ms   7ms

         11   94.16.100.32    7ms   7ms   7ms

         12 162.220.223.23    8ms   7ms   8ms

      Traceroute for ultra low latency secondary IPv4 (66.135.25.157)

          1   192.168.7.77    0ms   0ms   0ms

          2   32.221.200.1    2ms   2ms   1ms

          3   172.76.21.25    2ms   2ms   2ms

          4  45.52.201.234    5ms   6ms   6ms

          5  74.41.143.173    5ms   5ms   5ms

          6     4.68.10.29   10ms   7ms   7ms

          7                   *     *     *

          8    65.59.14.18    *     9ms   9ms

          9                   *     *     *

         10                   *     *     *

         11                   *     *     *

         12  66.135.25.157    8ms   7ms   8ms

      Traceroute for anycast primary IPv4 (45.90.28.0)

          1   192.168.7.77    0ms   0ms   0ms

          2   32.221.200.1    2ms   2ms   2ms

          3   172.76.21.25    2ms   2ms   2ms

          4  45.52.201.234    6ms   6ms   6ms

          5  74.41.143.173   14ms  14ms   7ms

          6     4.68.10.29    *    21ms   6ms

          7    4.69.134.30   14ms  13ms  13ms

          8    4.15.18.246   13ms  16ms  14ms

          9 185.206.226.106   29ms  36ms  49ms

         10  193.9.115.223   14ms  14ms  14ms

         11  45.11.107.159   14ms  14ms  14ms

         12     45.90.28.0   14ms  14ms  14ms

      Traceroute for anycast secondary IPv4 (45.90.30.0)

          1   192.168.7.77    0ms   0ms   0ms

          2   32.221.200.1    1ms   2ms   2ms

          3   172.76.21.25    2ms   3ms   2ms

          4  45.52.201.234    6ms   6ms   6ms

          5  74.41.143.173   14ms  11ms   9ms

          6     4.68.10.29    7ms   7ms  11ms

          7                   *     *     *

          8    4.16.75.182   11ms  11ms  11ms

          9 213.227.177.32   11ms  11ms  11ms

         10     45.90.30.0   24ms  11ms  11ms

      Do you want to send this report? [Y/n]: 

Login to reply

Content aside

  • 2 wk agoLast active
  • 3Replies
  • 95Views
  • 4 Following