|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: Microsoft spokesperson blames ICANN
What's with all the articles that say alot, but really tell us nothing? DNS is not rocket science. The root-servers and gtld-servers I checked all report the same set of NS records for microsoft.com: ;; ANSWER SECTION: microsoft.com. 2D IN NS DNS4.CP.MSFT.NET. microsoft.com. 2D IN NS DNS5.CP.MSFT.NET. microsoft.com. 2D IN NS DNS7.CP.MSFT.NET. microsoft.com. 2D IN NS DNS6.CP.MSFT.NET. ;; ADDITIONAL SECTION: DNS4.CP.MSFT.NET. 2D IN A 207.46.138.11 DNS5.CP.MSFT.NET. 2D IN A 207.46.138.12 DNS7.CP.MSFT.NET. 2D IN A 207.46.138.21 DNS6.CP.MSFT.NET. 2D IN A 207.46.138.20 These four systems are pingable, but don't seem to be answering DNS requests. So...are these NS records for microsoft.com incorrect (someone botched microsoft.com in the .com zone either by accident or malice)...or are they correct and microsoft can't figure out how to run their DNS servers? Either way, these addresses are Microsoft's (according to ARIN), so it would appear Microsoft can't come up with a backup plan of some sort when their DNS servers hit the fan, and they're spokespeople are basically feeding the press a load of crap and misdirection? Or maybe their DNS servers are under some sort of DoS attack flooding them with so many DNS requests that they just can't handle the load and they can't filter the attack because the source addresses are randomly forged and they can't tell the difference between real requests and DoS requests? Why bother writing crap news stories that really just say Microsoft is down, but don't say anything about the cause? -- ---------------------------------------------------------------------- Jon Lewis *[email protected]*| I route System Administrator | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
|