0

DNS Queries latency

Since a few weeks I noticed that my DNS queries are very, very slow when using NextDNS.
It looks like this is related to the DNS over HTTPS (encrypted DNS)

I have run the diag, will not post the diag URL here (as it contains my own IP):

Do you want to continue? (press enter to accept)
[sudo] password for daniel:
Testing IPv6 connectivity
  available: false
Fetching https://test.nextdns.io
  status: ok
  client: 84.83.153.177
  protocol: DOH
  dest IP: 45.90.28.168
  server: zepto-ams-2
Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
  vultr-ams: 5.399ms
Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
  anexia-ams: 31.094ms
Fetching PoP name for anycast primary IPv4 (45.90.28.0)
  zepto-ams: 5.329ms
Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
  vultr-ams: 3.93ms
Pinging PoPs
  zepto-bru: 5.623ms
  zepto-ams: 22.328ms
  zepto-ams: 11.532ms
  anexia-lux: 24.08ms
  vultr-ams: 23.338ms
  anexia-lon: 29.027ms
  zepto-lon: 31.015ms
  vultr-lon: 32.567ms
  fusa-bru: 50.603ms
  anexia-ams: 50.96ms
Traceroute for ultra low latency primary IPv4 (95.179.134.211)
    1    172.26.16.1    0ms   0ms   0ms
    2    192.168.3.1    0ms   2ms   0ms
    3 195.190.228.155    2ms   2ms   2ms
    4    81.20.65.10  105ms 102ms 103ms
    5                   *     *     *
    6   129.250.7.86    *     *    17ms
    7   129.250.2.11    7ms   7ms   7ms
    8   81.20.72.122    8ms   8ms   8ms
    9                   *     *     *
   10                   *     *     *
   11                   *     *     *
   12 95.179.134.211    7ms   7ms   7ms
Traceroute for ultra low latency secondary IPv4 (188.172.219.167)
    1    172.26.16.1    0ms   0ms   0ms
    2    192.168.3.1    0ms   0ms   0ms
    3 195.190.228.155    4ms   2ms   2ms
    4                   *     *     *
    5                   *     *     *
    6   81.20.65.242    9ms  10ms  10ms
    7 144.208.208.156   12ms  12ms  12ms
    8 188.172.219.167   12ms  12ms  11ms
Traceroute for anycast primary IPv4 (45.90.28.0)
    1    172.26.16.1    0ms   0ms   0ms
    2    192.168.3.1    0ms   0ms   0ms
    3 195.190.228.155    3ms   2ms   2ms
    4                   *     *     *
    5                   *     *     *
    6   81.20.69.166    5ms   4ms   4ms
    7                   *     *     *
    8  93.189.61.194    5ms   5ms   5ms
    9     45.90.28.0    5ms   5ms   4ms
Traceroute for anycast secondary IPv4 (45.90.30.0)
    1    172.26.16.1    0ms   0ms   0ms
    2    192.168.3.1    0ms   0ms   0ms
    3 195.190.228.155    3ms   2ms   2ms
    4                   *     *     *
    5                   *     *     *
    6  129.250.2.162   24ms  30ms  26ms
    7   129.250.2.11   27ms   6ms   5ms
    8   81.20.72.122    7ms   6ms   6ms
    9                   *     *     *
   10                   *     *     *
   11                   *     *     *
   12     45.90.30.0    4ms   3ms   4ms
Do you want to send this report? [Y/n]: y

3 replies

null
    • Daaaan
    • 1 mth ago
    • Reported - view

    Without NextDNS:

    Do you want to continue? (press enter to accept)
    Testing IPv6 connectivity
      available: false
    Fetching https://test.nextdns.io
      status: ok
      client: 84.83.153.177
      protocol: UDP
      dest IP: 45.90.28.74
      server: zepto-ams-2
    Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
      zepto-ams: 5.136ms
    Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
      vultr-ams: 5.695ms
    Fetching PoP name for anycast primary IPv4 (45.90.28.0)
      zepto-ams: 5.828ms
    Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
      vultr-ams: 3.776ms
    Pinging PoPs
      zepto-ams: 5.645ms
      zepto-bru: 6.234ms
      vultr-ams: 18.587ms
      zepto-ams: 18.673ms
      vultr-lon: 36.275ms
      zepto-lon: 32.4ms
      fusa-bru: 36.263ms
      anexia-lon: 33.954ms
      anexia-lux: 35.304ms
      anexia-ams: 69.465ms
    Traceroute for ultra low latency primary IPv4 (93.189.61.195)
        1    172.26.16.1    0ms   0ms   0ms
        2    192.168.3.1    0ms   0ms   0ms
        3 195.190.228.155    3ms   2ms   2ms
        4                   *     *     *
        5                   *     *     *
        6  93.189.61.194    5ms   5ms   5ms
        7  93.189.61.195    5ms   5ms   5ms
    Traceroute for ultra low latency secondary IPv4 (95.179.134.211)
        1    172.26.16.1    0ms   0ms   0ms
        2    192.168.3.1    2ms  15ms   0ms
        3 195.190.228.155    8ms   3ms   3ms
        4                   *     *     *
        5                   *     *     *
        6   129.250.7.86    6ms   5ms   6ms
        7   129.250.2.11    9ms  12ms  11ms
        8   81.20.72.122    8ms  14ms  18ms
        9                   *     *     *
       10                   *     *     *
       11                   *     *     *
       12 95.179.134.211    8ms   8ms   8ms
    Traceroute for anycast primary IPv4 (45.90.28.0)
        1    172.26.16.1    0ms   0ms   0ms
        2    192.168.3.1    1ms   0ms   1ms
        3 195.190.228.155    4ms   2ms   2ms
        4                   *     *     *
        5                   *     *     *
        6   81.20.69.166    4ms   4ms   5ms
        7                   *     *     *
        8  93.189.61.194    5ms   4ms   6ms
        9     45.90.28.0    4ms   4ms   7ms
    Traceroute for anycast secondary IPv4 (45.90.30.0)
        1    172.26.16.1    0ms   0ms   0ms
        2    192.168.3.1    0ms   0ms   0ms
        3 195.190.228.155    9ms   2ms   2ms
        4                   *     *     *
        5                   *     *     *
        6                   *     *     *
        7   129.250.2.11    6ms   9ms   5ms
        8   81.20.72.122   28ms  15ms   6ms
        9                   *     *     *
       10                   *     *     *
       11                   *     *     *
       12     45.90.30.0    3ms   3ms   7ms

    • NextDNs
    • 1 mth ago
    • Reported - view

    It looks pretty good from the diag. What makes you think DNS is slow?

    • Christophe_Yayon
    • 1 mth ago
    • Reported - view

    Hi,

    same issue on secondary DNS  from France (see my other post).

    the issue was solved (due to NTT network) since 2 or 3 days and is back again. 

Content aside

  • 1 mth agoLast active
  • 3Replies
  • 75Views
  • 3 Following