failing IPv6 ping to a.root-servers.net
My probe #35105's builtin test "#2009 Ping to a.root-servers.net (2001:503:ba3e::2:30)" fail most of the time while IPv6 pings to other targets work just fine. From poking around other probes, this seems to be a common problem. I wonder if this is why my probe never keeps its "IPv6 Stable 1d" tag for long when it does eventually get it. The way I see it, that one failing test set puts the probe below the 95% working cutoff for IPv6. Are other people seeing the same failing ping6 to a.root-servers.net? 2018-01-25 12:33:27 UTC Probe auto-untagged Your probe #35105 was automatically untagged as "system: IPv6 Stable 1d" 2018-01-25 08:35:56 UTC Probe auto-tagged Your probe #35105 was automatically tagged as "system: IPv6 Stable 1d" -wolfgang
Hello, On 3.2.2018 0:11, Wolfgang S Rupprecht wrote:
Are other people seeing the same failing ping6 to a.root-servers.net?
For my ipv6 capable probe it has been the j-root not answering v6 pings since the beginning of October 2017. The a-root my probe ends at was also not replying to v6 pings from October 2017 to December 2017 and intermittently since then. Both roots are operated by Verisign, maybe they have configs at some of their anycast sites that drop v6 ping. They do answer dns queries for me when I've tried it from a machine in the same network as the probe. I have also noticed the ipv6 stable tags coming and going, maybe this has something to do with it. Tapio
participants (2)
-
Tapio Sokura -
Wolfgang S Rupprecht