-----BEGIN PGP SIGNED MESSAGE----- Why should only misspelt domains lookups go to him? If nameservers found the additional root-NSs during the time they were announced, they would have started to using them as much as all the other root-ns, at least until they had enough data to make the RTT decisions on which are preferred, no? - -----Original Message----- From: Ryan K. Brooks <ryan@inc.net> To: Craig A. Huegen <chuegen@quadrunner.com> Cc: max@inc.net <max@inc.net>; nanog@merit.edu <nanog@merit.edu> Date: Tuesday, August 18, 1998 4:20 AM Subject: Re: DNS Headaches. | | | | |Craig A. Huegen wrote: | |> This wouldn't be webteam.net, would it? =) |> |> This morning, Chris Yarnell from NASA pointed out the response |> to "dig @a.root-servers.net . soa": |> |> . 2D IN NS PANIC.WEBTEAM.NET. |> . 2D IN NS TORGO.WEBTEAM.NET. |> PANIC.WEBTEAM.NET. 2D IN A 207.67.50.8 |> TORGO.WEBTEAM.NET. 2D IN A 207.67.50.7 |> |> I don't know how this happened, but it doesn't look pretty. =) |> |> (The "standard" zone files were okay -- .COM, .NET, etc...) |> |> /cah | |How did this happen anyway? InterNIC? Postel? Doesn't this error imply that |a percentage of the Internet was unresolvable by the entire planet? | |It would really be great to find out what chain of events got us a root |nameserver on our network; not that we wouldn't mind donating the resources |to run one - it would just be nice to know in advance. :-) | | |Maybe we can get bilateral peering with BBN since we have a root server, | | |Ryan Brooks |ryan@inc.net |CTO, Internet Connect, Inc. | | | -----BEGIN PGP SIGNATURE----- Version: PGP 5.5.5 iQB1AwUBNdhMeVUjujkl4IK9AQGKdAL/YtGzleIfxiArvw7clyMDp/447uQg/FGB xkYr8JWdh+oxgR00zoParhGMtjK1PABf0UEIR3+fT/Us4PKJOIwJbqu1Ca/ZvSqP OSOcmxBSuwr8zXe1PNdzuT2lyvniVZZf =5cvS -----END PGP SIGNATURE-----