And what they don't explain is that there is a good reason for that."As best we can tell, no user noticed and the attack was dealt with and life goes on," said Louis Touton, vice president for the Internet Corporation for Assigned Names and Numbers, the Internet's key governing body.
Pretty much all the root servers do is tell DNS servers around the Internet which DNS servers server the .com zone and other TLDs. The root servers do little more than that (they also serve the in-addr.arpa domain and .edu/.gov, I believe). The TLD NS records are cached for 48 hours, and since the attack only lasted for an hour, only a small percent of DNS servers in the world would need to have contacted the root servers during that time. Those that did would try the 6 root servers that were not shut down by the attack (which would certainly be much busier than normal, but should respond). So someone trying to go to a website with a foreign TLD ( http://www.example.co.uk, for example) might have experienced a slight delay -- but then anyone after him using the same DNS server would have no problems reaching .uk domains for another 48 hours.
If this had happened with the gTLD (.com, .net, .org, .etc) servers, it would have been much more noticeable.
-Scott
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
