0

NextDNS unusably slow today

Hi

NextDNS annual paid sub here.

 

I woke up today to find nextdns being incredibly slow. Checked router, fine, changed dns to quad9 and it works perfectly.

Nextdns won't even resolve google.com sometimes, it just times out.

Apparently I'm on Vultr London.

Completely unsure what to do now, I've had to turn it off as none of my devices will work.

ping.nextdns.io errored out

test.nextdns.io wouldn't even resolve

cli ping nextdns.io didn't work

cli ping google.com did

Checked my filters and nothing changed or blocking everything etc

I've added screenshots including what dns servers dnsleak shows

help please

2 replies

null
    • thesmileyone
    • 8 mths ago
    • Reported - view

    cli diag

     

    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)
[sudo] password for XXXXXXX:
Resolvers:  192.168.178.1
Testing IPv6 connectivity
  available: false
Fetching https://test.nextdns.io
  Fetch error: Get "https://test.nextdns.io": dial tcp: lookup test.nextdns.io on [fd00::de15:c8ff:fe1c:deb3]:53: read udp 192.168.178.26:36843->192.168.178.1:53: i/o timeout
Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
  anexia-lon: 13.95ms
Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
  zepto-lon: 11.537ms
Fetching PoP name for anycast primary IPv4 (45.90.28.0)
  vultr-lon: 10.554ms
Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
  anexia-lon: 11.341ms
Pinging PoPs
  anexia-lon: 11.413ms
  vultr-lon: 11.254ms
  zepto-lon: 10.868ms
  zepto-ams: 17.225ms
  netbarista-par: 18.903ms
  zepto-bru: 19.332ms
  vultr-ams: 19.113ms
  fusa-bru: 25.451ms
  anexia-ams: 24.89ms
  anexia-par: 28.494ms
Traceroute for ultra low latency primary IPv4 (37.252.230.153)
    1  192.168.178.1    1ms   1ms   1ms
    2  51.148.77.129   11ms  12ms  14ms
    3   51.148.73.91   11ms  11ms  10ms
    4 195.66.226.113   11ms  10ms  11ms
    5 37.252.230.153   11ms  11ms  10ms
Traceroute for ultra low latency secondary IPv4 (45.142.244.191)
    1  192.168.178.1    2ms   1ms   1ms
    2  51.148.77.129   14ms  12ms  12ms
    3   51.148.73.91   11ms  10ms  11ms
    4    5.57.80.242   11ms  10ms  10ms
    5    5.226.136.8   11ms  15ms  11ms
    6   45.11.107.74   11ms  11ms  11ms
    7   45.142.244.4   10ms  10ms  12ms
    8 45.142.244.191   11ms  11ms  10ms
Traceroute for anycast primary IPv4 (45.90.28.0)
    1  192.168.178.1    *     1ms   1ms
    2  51.148.77.129   14ms  15ms  13ms
    3   51.148.73.91   12ms  10ms  11ms
    4 213.248.102.244    *     *    12ms
    5   62.115.58.26   11ms  11ms  11ms
    6                   *     *     *
    7                   *     *     *
    8                   *     *     *
    9     45.90.28.0   11ms  10ms  11ms
Traceroute for anycast secondary IPv4 (45.90.30.0)
    1  192.168.178.1    1ms   1ms   1ms
    2  51.148.77.129   15ms  11ms  13ms
    3   51.148.73.91   12ms  12ms  10ms
    4 195.66.226.113   11ms  11ms  11ms
    5     45.90.30.0  117ms  11ms  13ms
Do you want to send this report? [Y/n]: y
Optional email in case we need additional info: xxxxx@xxxxxx.xxx
Post unsuccessful: status 400
{"error":"0: instance.Test requires property \"Client\"\n"}[xxxx@xxxxx-xxxx ~]$
    • NextDNs
    • 8 mths ago
    • Reported - view

    Please try the diag with nextdns disabled

Login to reply

Content aside

  • 8 mths agoLast active
  • 2Replies
  • 205Views
  • 2 Following