[dns-wg] f.root-servers.net unreachable for a few days?
- Previous message (by thread): [dns-wg] f.root-servers.net unreachable for a few days?
- Next message (by thread): [dns-wg] [dns-operations] Additional information about the RIPE NCC reverse DNS issue
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Max Grobecker
max.grobecker at ml.grobecker.info
Sun Mar 19 14:18:19 CET 2017
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 > > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <https://lists.ripe.net/ripe/mail/archives/dns-wg/attachments/20170319/aaf6c76c/attachment.sig>
- Previous message (by thread): [dns-wg] f.root-servers.net unreachable for a few days?
- Next message (by thread): [dns-wg] [dns-operations] Additional information about the RIPE NCC reverse DNS issue
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]