0

Issues with anycast and dns2 availability

Hello,

I have been seeing repeated failures and outages with anycast dns.nextdns.io and dns2.nextdns.io in Dubai. Also, it seems the diagnostic test isn't properly detecting the presence of IPv6 service.

Currently using xxxxx.dns2.nextdns.io as the anycast address isn't working as expected.

Logs are littered with "timeout: no recent network activity" and I've tried connecting over h3, https, DoQ and DoT.

 

Please look into this.

https://nextdns.io/diag/cac058b0-85db-11ef-93f0-b7924f87a175

Thanks

Wiz

10 replies

null
    • NextDNs
    • 1 mth ago
    • Reported - view

    Can you please try again?

      • Wiz
      • 1 mth ago
      • Reported - view

       No change, same issue...

       

      ;; communications error to 127.0.0.1#53: timed out
      ;; communications error to 127.0.0.1#53: timed out
      ;; communications error to 127.0.0.1#53: timed out
      
      ; <<>> DiG 9.18.24 <<>> google.com
      ;; global options: +cmd
      ;; no servers could be reached

       

      https://nextdns.io/diag/1a9a5950-86cf-11ef-b2eb-dd41169b4535

      Both xxxx.dns2.nextdns.io and xxxxxx.dns.nextdns.io fail! Tried them separately and as fallback. Only dns1 is working.

      • Wiz
      • 1 mth ago
      • Reported - view

       The issue is also present while testing from multiple separate endpoints in Dubai.

      No issues with Cloudflare or other DoQ/DoT/H3 managed dns providers.

    • NextDNS_Network
    • 1 mth ago
    • Reported - view

    Could you please run a traceroute or MTR towards the following IP addresses to help us further diagnose the connectivity issues?

    mtr --report-wide --show-ips 37.252.245.241
    mtr --report-wide --show-ips 37.252.245.1
    mtr --report-wide --show-ips 37.252.245.20

     

    We have reviewed the routing on our end and found no issues, so the problem may originate from your ISP. These additional tests will help us confirm this. Please send us the results once you have them.

      • Wiz
      • 1 mth ago
      • Reported - view

       Here you go:

       

      root@edge:~# mtr --report-wide --show-ips 37.252.245.241
      Start: 2024-10-12T09:21:48+0400
      HOST: edge                                          Loss%   Snt   Last   Avg  Best  Wrst StDev
        1.|-- lan (10.20.30.1)                 0.0%    10    0.7   0.8   0.7   0.9   0.0
      2.|-- bba-86-99-216-1.alshamil.net.ae (86.99.216.1) 0.0% 10 3.3 3.5 3.1 5.8 0.8
        3.|-- ???                                           100.0    10    0.0   0.0   0.0   0.0   0.0

      root@edge:~# mtr --report-wide --show-ips 37.252.245.1

      Start: 2024-10-12T09:22:24+0400
      HOST: edge                                          Loss%   Snt   Last   Avg  Best  Wrst StDev
        1.|-- lan (10.20.30.1)                 0.0%    10    0.8   0.8   0.7   0.9   0.1
      2.|-- bba-86-99-216-1.alshamil.net.ae (86.99.216.1) 0.0% 10 3.9 4.5 3.1 12.7 2.9
        3.|-- 10.246.255.125 (10.246.255.125)                0.0%    10    3.1   4.2   3.1   7.5   1.6
        4.|-- 195.229.4.106 (195.229.4.106)                  0.0%    10    5.2   5.3   4.8   5.8   0.3
        5.|-- 195.229.0.236 (195.229.0.236)                  0.0%    10    5.4   5.2   4.7   5.6   0.3
        6.|-- 185.1.15.54 (185.1.15.54)                      0.0%    10    8.1   8.5   8.0   8.9   0.4
      7.|-- j48-2.dx1.dxb.ae.datamena.net (94.207.42.34) 0.0% 10 9.1 8.6 8.1 9.1 0.3
      8.|-- oobfw1-dxb1-dx.uae-ix.net (94.207.34.34) 0.0% 10 8.5 8.8 8.5 9.3 0.3
        9.|-- ???                                           100.0    10    0.0   0.0   0.0   0.0   0.0

      root@edge:~# mtr --report-wide --show-ips 37.252.245.20
      Start: 2024-10-12T09:23:06+0400
      HOST: edge                                          Loss%   Snt   Last   Avg  Best  Wrst StDev
        1.|-- lan (10.20.30.1)                 0.0%    10    0.8   0.8   0.7   1.0   0.1
      2.|-- bba-86-99-216-1.alshamil.net.ae (86.99.216.1) 0.0% 10 3.9 5.2 3.3 12.3 3.2
        3.|-- 10.246.255.125 (10.246.255.125)                0.0%    10    3.1   3.5   3.1   4.9   0.5
        4.|-- 195.229.4.106 (195.229.4.106)                  0.0%    10    5.4   6.4   4.3  16.3   3.5
        5.|-- 195.229.0.236 (195.229.0.236)                  0.0%    10    5.4   5.5   5.0   6.0   0.3
        6.|-- 185.1.15.54 (185.1.15.54)                      0.0%    10    7.3   7.3   6.9   7.9   0.3
      7.|-- j48-2.dx1.dxb.ae.datamena.net (94.207.42.34) 0.0% 10 7.3 7.6 7.1 9.7 0.8
      8.|-- oobfw1-dxb1-dx.uae-ix.net (94.207.34.34) 0.0% 10 7.3 7.4 7.0 7.8 0.2
      9.|-- anx-lg-ae-dxb01.anexia-it.com (37.252.245.20) 0.0% 10 7.7 7.7 7.4 8.1 0.2

      I believe the issue is with dns2 node's IPv4 as I can ping its IPv6 advertised address. Additionally, xxxx.dns.nextdns.io is failing instead of properly steering to the only working node in dubai dns1 and including the next available nearest node ie. ruh

      As stated previously, I have no issues with other managed dns providers .. some with nodes in Dubai so I know the issue isn't with my ISP or edge/endpoints.

      I first noticed the issue about 2 weeks ago and thought it might be a temporary outage of some sort that would resolve on its own but it hasn't.

      • Wiz
      • 1 mth ago
      • Reported - view

        dns2's IPv6

      root@edge:~# mtr --report-wide --show-ips 2a00:11c0:14:506::9
      Start: 2024-10-12T09:58:49+0400
      HOST: edge                                                                Loss%   Snt   Last   Avg  Best  Wrst StDev
        1.|-- 2001:8f8:1363:511::1 (2001:8f8:1363:511::1)                          0.0%    10    1.0   1.0   0.6   1.2   0.1
        2.|-- 2001:8f8:3:1000::29 (2001:8f8:3:1000::29)                            0.0%    10    3.9   4.4   2.6   9.3   2.0
        3.|-- 2001:8f8:3:1107::1 (2001:8f8:3:1107::1)                              0.0%    10    3.8   5.0   3.3  17.0   4.2
        4.|-- 2001:8f8:0:10:0:23:204:1 (2001:8f8:0:10:0:23:204:1)                  0.0%    10    5.7   5.4   4.6   6.0   0.4
        5.|-- 2001:8f8:0:11:0:22:3:6 (2001:8f8:0:11:0:22:3:6)                      0.0%    10    8.0   7.8   7.4   8.8   0.5
        6.|-- ???                                                                 100.0    10    0.0   0.0   0.0   0.0   0.0
      7.|-- du-01.alb.dxb.ae.datamena.net (2a00:f28:2:202::1) 10.0% 10 82.4 82.4 81.7 83.0 0.4
      8.|-- j48-3.dx1.dxb.ae.datamena.net (2a00:f28:2:202::2) 10.0% 10 82.1 82.1 81.9 82.4 0.1
        9.|-- 2a00:f2f:1:3904:0:ffff:5ecf:2a31 (2a00:f2f:1:3904:0:ffff:5ecf:2a31) 10.0%    10   81.4  81.5  81.0  84.1   1.0
       10.|-- 2a00:f2f:11ff:5::2 (2a00:f2f:11ff:5::2)                             10.0%    10   12.8  12.3  11.4  12.8   0.4
       11.|-- 2a00:11c0:14:2:: (2a00:11c0:14:2::)                                 10.0%    10   16.1  16.3  16.1  16.6   0.2
      12.|-- dns.nextdns.io (2a00:11c0:14:506::9) 0.0% 10 12.0 12.2 11.9 12.8 0.3

    • Wiz
    • 1 mth ago
    • Reported - view

    Any update?

    • Wiz
    • 3 wk ago
    • Reported - view

    Was great when it worked! Won't be renewing next year.

    • David_B
    • 3 wk ago
    • Reported - view

    I think this is beginning of the end. Days long service interruptions without a word speaks volumes.  I've moved to Control D.

      • Wiz
      • 3 wk ago
      • Reported - view

       Yeah, I just finished setting up Control D in parallel mode, and thankfully, there’s a local node with single-digit latency. The plan is to gradually transition my endpoints and devices from NextDNS. Hopefully, the grass is greener on the other side.

Content aside

  • 3 wk agoLast active
  • 10Replies
  • 130Views
  • 4 Following