That'll teach me not to ignore the first lesson in all the 'security awareness' classes. If something seems odd, it probally is, and should be reported. Name resolution was sluggish enough I thought Hmm? when I first logged in yesterday. But the name resolved, and I had fun-filled day pending with the United States Post Office about something else so the odd DNS delay was quickly forgotten. Any reports if this was just an "Oops"(tm), or another Kasporov-type incident? a.root-servers.net is running BIND 8.1.2-T3B. I didn't notice any security patches between the beta and the final release of 8.1.2.

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...) -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation