0

IPv6 Non-ideal Routing Anycast2 (anexia-jnb)

My ISP is A&A in the UK and I'm getting routed to Johannesburg `anexia-jnb` for Anycast2, which is slow routing for London.

I can't submit Diag because it isn't detecting IPv6 for some reason but two traceroute6 below illustrate the problem. Anycast1 (2a07:a8c0) works correctly, but Anycast2 (2a07:a8c1) is problematic.

$ traceroute6 2a07:a8c1::xx:xxxx # Anycast2 where xx:xxxx is my ID
traceroute6 to 2a07:a8c1::xx:xxxx (2a07:a8c1::xx:xxxx) from 2001:8b0:dc1b:1da1:b98b:f51d:11f0:ada6, 64 hops max, 12 byte packets
1  1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.a.d.1.b.1.c.d.0.b.8.0.1.0.0.2.ip6.arpa  15.114 ms  3.145 ms  2.955 ms
2  t.gormless.thn.aa.net.uk  8.748 ms  8.312 ms  143.489 ms
3  o.aimless.tch.aa.net.uk  8.828 ms  9.997 ms  8.757 ms
4  2001:7f8:4::90ec:2  10.872 ms  109.910 ms  37.378 ms
5  ae-5-0.er6-05-lhr.uk.seacomnet.com  373.632 ms  187.144 ms  327.222 ms
6  xe-0-0-0-2.cr6-01-lhr.uk.seacomnet.com  351.944 ms
    xe-0-0-0-2.cr6-02-lhr.uk.seacomnet.com  173.502 ms  202.677 ms
7  xe-0-0-0-3.cr6-02-cpt.za.seacomnet.com  199.390 ms
    2c0f:feb0:1:2::b01  240.103 ms  177.478 ms
8  ce-1-1-5.cr6-02-jnb.za.seacomnet.com  277.460 ms  195.512 ms
    ce-0-1-1.cr6-01-jnb.za.seacomnet.com  312.323 ms
9  ae-6.er6-02-jnb.za.seacomnet.com  166.255 ms
    ae-5.er6-02-jnb.za.seacomnet.com  269.462 ms
    ae-6.er6-02-jnb.za.seacomnet.com  166.132 ms
10  2c0f:feb0:b:3::4fa  324.247 ms  225.460 ms  269.876 ms
11  2a00:11c0:67:2::  170.821 ms  186.958 ms  171.511 ms

 

$ traceroute6 2a07:a8c0::xx:xxxx # Anycast1 where xx:xxxx is my ID
traceroute to 2a07:a8c0::xx:xxxx (2a07:a8c0::xx:xxxx) from 2001:8b0:dc1b:1da1:294e:39be:e765:1ccd, 30 hops max, 24 byte packets
1  1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.a.d.1.b.1.c.d.0.b.8.0.1.0.0.2.ip6.arpa (2001:8b0:dc1b:1da1::1)  8.1005 ms  2.4926 ms  2.1301 ms
2  t.gormless.thn.aa.net.uk (2001:8b0:0:53::127)  7.2522 ms  6.7233 ms  7.2505 ms
3  ntt.a.needless.tch.aa.net.uk (2001:728:0:5000::67e)  9.5123 ms  8.3970 ms  7.1899 ms
4  xe-0-0-0-3-7.r04.londen05.uk.bb.gin.ntt.net (2001:728:0:5000::67d)  125.3429 ms  132.2174 ms  8.6805 ms
5  ae-7.r20.londen12.uk.bb.gin.ntt.net (2001:728:0:2000::5d)  122.3148 ms  7.6642 ms  8.1826 ms
6  ae-0.a02.londen12.uk.bb.gin.ntt.net (2001:728:0:2000::26a)  8.0009 ms  8.1105 ms  8.1410 ms
7  xe-0-3-0-0.a02.londen12.uk.ce.gin.ntt.net (2001:728:0:5000::bea)  8.9349 ms  9.2287 ms  8.0706 ms
8  ethernetae1-ds2-q8.lon3.constant.com (2001:19f0:fc00::a45:34a)  21.7037 ms  36.7474 ms  17.7380 ms
9  vl583-ds1-u3-r51b4-b.lon3.constant.com (2001:19f0:fc00::a45:aa)  8.3424 ms  9.1813 ms  8.3944 ms

Confirmed by ping.nextdns.io

  zepto-lon (IPv6)     9 ms
  anexia-lon           9 ms  (anycast2, ultralow1)
  vultr-lon (IPv6)     9 ms  (anycast1, ultralow2)
  zepto-lon            9 ms
■ vultr-lon            9 ms  (anycast1, ultralow2)
  anexia-lon (IPv6)    9 ms  (ultralow1)
  zepto-ams           14 ms
  vultr-ams (IPv6)    15 ms
  anexia-man          15 ms
  anexia-man (IPv6)   16 ms
  zepto-ams (IPv6)    16 ms
  vultr-ams           16 ms
  anexia-ams          21 ms
  anexia-ams (IPv6)   21 ms
  zepto-dub           23 ms
  fusa-bru            24 ms
  fusa-bru (IPv6)     26 ms
  anexia-dub (IPv6)   26 ms
  zepto-dub (IPv6)    38 ms
  anexia-dub          43 ms
  *anexia-jnb (IPv6)  167 ms  (anycast2)*

6 replies

null
    • NextDNS_Network
    • 2 yrs ago
    • Reported - view

    We have made some modifications to AnyCast2 IPv6 routing policy, please try again now.

    • S_M
    • 2 yrs ago
    • Reported - view

    Hi - thanks for getting back to me so quickly and for trying to make some adjustments. Much appreciated.

    I'm still seeing the same routing unfortunately - but maybe I need to wait for changes to propagate?

    Here's anycast.dns1.nextdns.io at 20:47 GMT 

    % traceroute6 anycast.dns1.nextdns.io
traceroute6 to anycast.dns1.nextdns.io (2a07:a8c0::) from 2001:8b0:dc1b:1da1:b98b:f51d:11f0:ada6, 64 hops max, 12 byte packets
 1  1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.a.d.1.b.1.c.d.0.b.8.0.1.0.0.2.ip6.arpa  6.642 ms  2.678 ms  2.588 ms
 2  t.gormless.thn.aa.net.uk  9.921 ms  10.848 ms  16.339 ms
 3  ntt.a.needless.tch.aa.net.uk  28.216 ms  34.260 ms  10.497 ms
 4  xe-0-0-0-3-7.r04.londen05.uk.bb.gin.ntt.net  9.418 ms  8.926 ms  9.351 ms
 5  ae-7.r20.londen12.uk.bb.gin.ntt.net  12.299 ms  8.819 ms  8.905 ms
 6  ae-0.a02.londen12.uk.bb.gin.ntt.net  19.263 ms  8.965 ms  9.049 ms
 7  xe-0-3-0-0.a02.londen12.uk.ce.gin.ntt.net  9.315 ms  9.441 ms  9.147 ms
 8  ethernetae1-ds2-q8.lon3.constant.com  10.880 ms
    ethernetae7-ds1-q8.lon3.constant.com  9.073 ms  12.430 ms
 9  vl582-ds1-u3-r51b4-a.lon3.constant.com  9.751 ms
    vl883-ds1-u3-r51b4-b.lon3.constant.com  9.051 ms  9.452 ms

     

    And here's anycast.dns2.nextdns.io 

    % traceroute6 anycast.dns2.nextdns.io
traceroute6 to anycast.dns2.nextdns.io (2a07:a8c1::) from 2001:8b0:dc1b:1da1:b98b:f51d:11f0:ada6, 64 hops max, 12 byte packets
 1  1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.a.d.1.b.1.c.d.0.b.8.0.1.0.0.2.ip6.arpa  3.172 ms  2.877 ms  2.817 ms
 2  t.gormless.thn.aa.net.uk  8.204 ms  9.396 ms  8.960 ms
 3  o.aimless.tch.aa.net.uk  8.523 ms  8.803 ms  8.788 ms
 4  2001:7f8:4::90ec:2  9.640 ms  9.604 ms  10.311 ms
 5  ae-5-0.er6-05-lhr.uk.seacomnet.com  171.595 ms  170.762 ms  170.721 ms
 6  xe-0-0-0-2.cr6-01-lhr.uk.seacomnet.com  166.046 ms
    xe-0-0-0-2.cr6-02-lhr.uk.seacomnet.com  166.959 ms  167.655 ms
 7  xe-0-7-0-0.cr6-02-cpt.za.seacomnet.com  171.035 ms
    xe-0-0-0-0.cr6-02-jnb.za.seacomnet.com  169.279 ms
    2c0f:feb0:1:2::af1  171.099 ms
 8  ce-0-1-1.cr6-01-jnb.za.seacomnet.com  170.546 ms  166.391 ms
    ce-1-1-5.cr6-02-jnb.za.seacomnet.com  178.315 ms
 9  ae-6.er6-02-jnb.za.seacomnet.com  171.641 ms  165.434 ms
    ae-5.er6-02-jnb.za.seacomnet.com  173.921 ms
10  2c0f:feb0:b:3::4fa  170.064 ms  165.350 ms  297.719 ms
11  2a00:11c0:67:2::  170.858 ms  165.510 ms  173.260 ms

     

    And here's ping.nextdns.io 

      vultr-lon (IPv6)     8 ms  (anycast1, ultralow2)
■ anexia-lon (IPv6)    9 ms  (ultralow1)
  zepto-lon            9 ms
  anexia-lon           9 ms  (anycast2, ultralow1)
  vultr-lon            9 ms  (anycast1, ultralow2)
  zepto-lon (IPv6)    10 ms
  vultr-ams           15 ms
  zepto-ams           15 ms
  anexia-man (IPv6)   15 ms
  anexia-man          16 ms
  vultr-ams (IPv6)    16 ms
  zepto-ams (IPv6)    17 ms
  anexia-dub          18 ms
  anexia-dub (IPv6)   18 ms
  zepto-dub (IPv6)    18 ms
  zepto-dub           19 ms
  anexia-ams          21 ms
  anexia-ams (IPv6)   21 ms
  fusa-bru            22 ms
  fusa-bru (IPv6)     26 ms
 *anexia-jnb (IPv6)  170 ms  (anycast2)*

    Not sure if it helps (and I don't understand networking very well at all so forgive me if this is expected), but the `dig -x` results are different for me for the two addresses 

    % dig -x 2a07:a8c1:: # Gets an answer for dns2 IPv6 address
; <<>> DiG 9.10.6 <<>> -x 2a07:a8c1::
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9504
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1  ;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.c.8.a.7.0.a.2.ip6.arpa. IN PTR
;; ANSWER SECTION:
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.c.8.a.7.0.a.2.ip6.arpa. 300 IN PTR dns2.nextdns.io.  ;; Query time: 54 msec
;; SERVER: fdc9:a26:3e41::1#53(fdc9:a26:3e41::1)
;; WHEN: Tue Dec 27 20:48:50 GMT 2022


% dig -x 2a07:a8c0:: # No answer for dns1 IPv6 address
; <<>> DiG 9.10.6 <<>> -x 2a07:a8c0::
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38665
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1  ;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.c.8.a.7.0.a.2.ip6.arpa. IN PTR  ;; AUTHORITY SECTION:
0.a.2.ip6.arpa.        1471    IN    SOA    pri.authdns.ripe.net. dns.ripe.net. 1672171573 3600 600 864000 3600  ;; Query time: 47 msec
;; SERVER: fdc9:a26:3e41::1#53(fdc9:a26:3e41::1)
;; WHEN: Tue Dec 27 20:48:56 GMT 2022
;; MSG SIZE  rcvd: 161
      • S_M
      • 2 yrs ago
      • Reported - view

      FYI - still the same this morning, routing via JNB for AnyCast2. Please LMK if I should try anything else.  

      % traceroute6 anycast.dns2.nextdns.io
traceroute6 to anycast.dns2.nextdns.io (2a07:a8c1::) from 2001:8b0:dc1b:1da1:b98b:f51d:11f0:ada6, 64 hops max, 12 byte packets
1  1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.a.d.1.b.1.c.d.0.b.8.0.1.0.0.2.ip6.arpa  3.116 ms  2.641 ms  29.458 ms
2  t.gormless.thn.aa.net.uk  9.088 ms  8.216 ms  8.092 ms
3  k-aimless.thn.aa.net.uk  8.025 ms  9.105 ms  8.189 ms
4  2001:7f8:4::90ec:2  9.326 ms  10.298 ms  36.465 ms
5  ae-5-0.er6-05-lhr.uk.seacomnet.com  170.005 ms  169.772 ms  539.250 ms
6  xe-0-0-0-2.cr6-02-lhr.uk.seacomnet.com  170.862 ms  171.522 ms  188.251 ms
7  2c0f:feb0:1:2::ad1  199.185 ms
    2c0f:feb0:1:2::ac1  237.597 ms
    2c0f:feb0:1:2::ad1  173.863 ms
8  ce-1-1-5.cr6-02-jnb.za.seacomnet.com  201.989 ms
    ce-0-1-1.cr6-01-jnb.za.seacomnet.com  174.486 ms
    ce-1-1-5.cr6-02-jnb.za.seacomnet.com  167.700 ms
9  ae-5.er6-02-jnb.za.seacomnet.com  279.307 ms
    ae-6.er6-02-jnb.za.seacomnet.com  185.877 ms  260.222 ms
10  2c0f:feb0:b:3::4fa  191.836 ms  311.246 ms  178.123 ms
11  2a00:11c0:67:2::  213.471 ms  164.955 ms  309.029 ms
    • S_M
    • 2 yrs ago
    • Reported - view

    Still seeing Anycast 2 IPv6 going to Johannesburg for London ISP. 

    Any thoughts? 

    ■ zepto-lon (IPv6)     8 ms  (ultralow1)
  anexia-lon (IPv6)    8 ms  (ultralow2)
  anexia-lon           8 ms  (anycast2, ultralow2)
  zepto-lon            8 ms  (ultralow1)
  vultr-lon            8 ms  (anycast1)
  vultr-lon (IPv6)    12 ms  (anycast1)
  vultr-ams           13 ms
  zepto-ams           13 ms
  anexia-man (IPv6)   14 ms
  anexia-man          16 ms
  zepto-ams (IPv6)    16 ms
  vultr-ams (IPv6)    18 ms
  anexia-dub          18 ms
  zepto-dub           19 ms
  zepto-dub (IPv6)    19 ms
  anexia-dub (IPv6)   19 ms
  anexia-ams (IPv6)   20 ms
  anexia-ams          20 ms
  fusa-bru            23 ms
  fusa-bru (IPv6)     24 ms
  anexia-jnb (IPv6)  177 ms  (anycast2)
      • NextDNS_Network
      • 2 yrs ago
      • Reported - view

      S M Sorry, could you try it again? It should work now.

    • S_M
    • 2 yrs ago
    • Reported - view

    Ooh - lovely - looks like it's all fixed! Thank you so much - really appreciate it.

    Going to AMS now instead of JNB, which is a fair bit closer. 

    % traceroute6 anycast.dns2.nextdns.io
traceroute6 to anycast.dns2.nextdns.io (2a07:a8c1::) from xxxx, 64 hops max, 12 byte packets
1  1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.a.d.1.b.1.c.d.0.b.8.0.1.0.0.2.ip6.arpa  209.504 ms  2.694 ms  1.900 ms
2  t.gormless.thn.aa.net.uk  7.918 ms  8.056 ms  10.731 ms
3  ntt.a.needless.tch.aa.net.uk  8.651 ms  7.786 ms  7.219 ms
4  xe-0-0-0-3-7.r04.londen05.uk.bb.gin.ntt.net  8.503 ms  9.204 ms  14.309 ms
5  ae-7.r20.londen12.uk.bb.gin.ntt.net  8.496 ms  7.941 ms  8.521 ms
6  ae-11.r20.amstnl07.nl.bb.gin.ntt.net  14.403 ms  14.178 ms  13.119 ms
7  ae-1.a00.amstnl08.nl.bb.gin.ntt.net  13.898 ms  19.708 ms  13.676 ms
8  xe-1-4-1-0.a00.amstnl08.nl.ce.gin.ntt.net  14.577 ms  14.074 ms  13.910 ms
9  vl22-er2-q8.ams1.constant.com  14.796 ms  14.613 ms  14.596 ms
10  vl567-ds2-u3-r7-1-68-b.ams1.constant.com  13.667 ms
    vl866-ds2-u3-r7-1-68-a.ams1.constant.com  14.823 ms  15.006 ms

    And here's ping.nextdns.io 

      anexia-lon (IPv6)   10 ms  (ultralow2)
  vultr-lon (IPv6)    12 ms  (anycast1)
  vultr-ams (IPv6)    13 ms  (anycast2)
  anexia-man (IPv6)   15 ms
  zepto-ams           16 ms
  vultr-ams           17 ms
  zepto-dub           18 ms
  zepto-dub (IPv6)    18 ms
  anexia-lon          19 ms  (anycast2, ultralow2)
  anexia-man          20 ms
■ zepto-lon (IPv6)    23 ms  (ultralow1)
  anexia-ams (IPv6)   23 ms
  anexia-ams          25 ms
  fusa-bru (IPv6)     28 ms
  vultr-lon           31 ms  (anycast1)
  fusa-bru            32 ms
  zepto-lon           34 ms  (ultralow1)
  zepto-ams (IPv6)    35 ms
  anexia-dub          46 ms
  anexia-dub (IPv6)  250 ms
Login to reply

Content aside

  • 2 yrs agoLast active
  • 6Replies
  • 116Views
  • 1 Following