0

anycast2 IPv6 is anexia-mow instead of anexia-lon!

Hello,

Once again, the IPv6 routing has screwed up from AANET. I don't understand why this keeps happening - it works for a variable amount of time, then breaks again.

IPv6 anycast 2 is now anexia-mow instead of anexia-lon, which also doesn't make sense - why has it jumped to a server so far away?

I can't provide a useful diag either because your IPv6 test is still failing - ipv6.test-ipv6.is unavailable so the diag assumes IPv6 is unavailable and this is the result: https://nextdns.io/diag/6f195480-acaf-11ef-9bf1-27e76a13fe5a

I did mention this the last time I reported an issue - you need to find a better way of detecting IPv6 than using a domain you don't control which may or may not vanish at some point.

MTR attached, that should be enough to show the issue.

Thanks,

-Will

                                                                My traceroute  [v0.95]
Achlys (2001:8b0:6401:82a0:943a:6776:d6c:bd5e) -> 2a07:a8c1:: (2a07:a8c1::)                                                  2024-11-27T11:00:04+0000
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                                                             Packets               Pings
 Host                                                                                                      Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. AS20712  router.z3n.uk                                                                                  0.0%    14    4.4   4.4   4.2   4.8   0.1
 2. AS20712  c.gormless.thn.aa.net.uk                                                                       0.0%    14   11.0  11.0   9.5  12.2   0.8
 3. AS???    2001:7f8:4::50e8:1                                                                             0.0%    14   11.3  10.9  10.1  11.8   0.6
 4. AS???    linx-224.retn.net                                                                              0.0%    13   47.7  20.6  11.3  47.7  12.1
 5. AS29470  2a02:24b0::2e2e:8413                                                                           0.0%    13   56.4  58.9  54.8  88.7   9.1
 6. AS29470  2a02:24b0:1100:5:232a::1                                                                       0.0%    13   66.6  58.0  56.1  66.6   2.7
 7. AS42473  2a00:11c0:1b:2::                                                                               0.0%    13   54.1  55.1  54.1  56.1   0.6
 8. AS34939  dns2.nextdns.io                                                                                0.0%    13   98.9  81.6  54.4 106.2  20.7

4 replies

null
    • NextDNs
    • 4 mths agoThu, November 28, 2024 at 2:25 AM UTC
    • Reported - view

    Please try the diag again. IPv6 should be fixed.

      • Will_Tisdale
      • 4 mths agoSun, December 1, 2024 at 7:13 PM UTC
      • Reported - view

      Nope, the diag is still not detecting IPv6 on two separate networks that have confirmed working IPv6.

      https://nextdns.io/diag/d7a49a80-b017-11ef-99bc-57c2374390f8

      Although the issue with the secondary is now resolved so this is a moot point:

                                                                      My traceroute  [v0.95]
Achlys (2001:8b0:6401:82a0:29ff:2222:c9ad:4e99) -> 2a07:a8c1:: (2a07:a8c1::)                                                 2024-12-01T19:10:50+0000
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                                                             Packets               Pings
 Host                                                                                                      Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. AS20712  router.z3n.uk                                                                                  0.0%    20    4.3   5.0   4.2  13.6   2.0
 2. AS20712  c.gormless.thn.aa.net.uk                                                                       0.0%    20   17.6  16.7  14.7  18.9   1.0
 3. AS2914   ntt.a.needless.tch.aa.net.uk                                                                   0.0%    20   17.2  16.9  15.5  18.6   0.8
 4. AS2914   xe-0-5-3-3.a01.londen17.uk.bb.gin.ntt.net                                                      0.0%    20   18.3  17.4  16.2  23.6   1.6
 5. AS2914   ae-3.r22.londen12.uk.bb.gin.ntt.net                                                            0.0%    19   17.9  17.4  15.9  20.7   1.1
 6. AS2914   ae-19.a03.londen12.uk.bb.gin.ntt.net                                                           0.0%    19   15.5  16.9  15.5  18.5   0.7
 7. AS2914   2001:728:0:5000::5ce                                                                           0.0%    19   16.6  17.8  15.5  28.8   2.8
 8. AS42473  2a00:11c0:8:2::                                                                                0.0%    19   18.1  19.1  16.2  30.3   3.9
 9. AS34939  dns2.nextdns.io                                                                                0.0%    19   17.6  17.3  16.1  20.1   0.9

      But the diag needs to correctly detect IPv6, which it doesn't.

      • NextDNs
      • 4 mths agoSun, December 1, 2024 at 9:52 PM UTC
      • Reported - view

       should be fixed now, for good this time.

      • Will_Tisdale
      • 3 mths agoMon, December 2, 2024 at 11:06 AM UTC
      • Reported - view

      It certainly is - thanks.

      https://nextdns.io/diag/79cb5220-b08d-11ef-bdda-253e3231d6b0

Login to reply

Content aside

  • 3 mths agoMon, December 2, 2024 at 12:36 PM UTCLast active
  • 4Replies
  • 41Views
  • 2 Following