f.root-servers.net unreachable for a few days?
Hello, I noticed that f.root-servers.net is unreachable via IPv4 from my test locations (most of them in Germany). Relying on RIPE ATLAS [1] I'm pretty sure I'm not alon with this "problem". A traceroute from my home DSL connection (DTAG, AS3320) shows that packets are surprisingly routed to somewhere in Pakistan and never get answered. Also Port 53/UDP/TCP is unresponsive. --------------------------------- traceroute to f.root-servers.net (192.5.5.241), 30 hops max, 60 byte packets 1 87.186.224.133 (87.186.224.133) [AS3320] 18.144 ms 2 87.190.177.174 (87.190.177.174) [AS3320] 18.843 ms 3 217.239.49.30 (217.239.49.30) [AS3320] 23.291 ms 4 te0-0-0-16.agr21.fra03.atlas.cogentco.com (130.117.14.149) [AS174] 33.528 ms 5 * 6 be2959.ccr21.muc03.atlas.cogentco.com (154.54.36.54) [AS174] 38.948 ms 7 be3072.ccr21.zrh01.atlas.cogentco.com (130.117.0.17) [AS174] 41.687 ms 8 be3080.ccr21.mrs01.atlas.cogentco.com (130.117.49.1) [AS174] 46.415 ms 9 be2345.agr21.mrs01.atlas.cogentco.com (154.54.38.170) [AS174] 46.891 ms 10 ptcl.demarc.cogentco.com (149.6.155.146) [*] 156.865 ms 11 static-10GE-KHI275-P01-SwA.pie.net.pk (202.125.128.173) [AS17557] 155.095 ms 12 221.120.251.178 (221.120.251.178) [AS17557] 153.854 ms 13 * 14 * 15 * 16 * 17 * --------------------------------- Has something happened to the F-Root instances in Europe? Or has the IP address changed? [1] https://atlas.ripe.net/results/maps/root-server-performance/?t=1489877040&server=4&transport=Compare&af=4&filter=# Greetings Max
On 18/03/2017 22:58, Max Grobecker wrote:
Hello,
I noticed that f.root-servers.net is unreachable via IPv4 from my test locations (most of them in Germany). Relying on RIPE ATLAS [1] I'm pretty sure I'm not alon with this "problem".
A traceroute from my home DSL connection (DTAG, AS3320) shows that packets are surprisingly routed to somewhere in Pakistan and never get answered. Also Port 53/UDP/TCP is unresponsive.
...
Has something happened to the F-Root instances in Europe? Or has the IP address changed?
Thanks for the report. We had problems a couple of days ago with what looked like a route leak from that site. We'll reinvestigate Ray
On 18/03/2017 22:58, Max Grobecker wrote:
I noticed that f.root-servers.net is unreachable via IPv4 from my test locations (most of them in Germany). Relying on RIPE ATLAS [1] I'm pretty sure I'm not alon with this "problem".
We've withdrawn our BGP routes from our Karachi node until such time as we can figure out the cause of the route leak and why the node was unresponsive. Thanks again for the report. Ray
Hi Ray, thank you - now it's reachable again via a short path :-) -------------------------- traceroute to f.root-servers.net (192.5.5.241), 30 hops max, 60 byte packets 1 87.186.224.133 (87.186.224.133) [AS3320] 18.373 ms 2 87.190.177.174 (87.190.177.174) [AS3320] 19.008 ms 3 217.239.43.217 (217.239.43.217) [AS3320] 23.451 ms 4 amsix.r2.ams1.isc.org (80.249.208.140) [AS1200] 24.194 ms 5 f.root-servers.net (192.5.5.241) [AS3357/AS3557/AS55440/AS23708/AS8167] 24.171 ms -------------------------- Have a nice weekend Max Am 19.03.2017 um 00:48 schrieb Ray Bellis:
On 18/03/2017 22:58, Max Grobecker wrote:
I noticed that f.root-servers.net is unreachable via IPv4 from my test locations (most of them in Germany). Relying on RIPE ATLAS [1] I'm pretty sure I'm not alon with this "problem".
We've withdrawn our BGP routes from our Karachi node until such time as we can figure out the cause of the route leak and why the node was unresponsive.
Thanks again for the report.
Ray
participants (2)
-
Max Grobecker -
Ray Bellis