[anybody who shows up for a job interview with a resume saying "router ops for microsoft" should be viewed warily] http://www.microsoft.com/info/siteaccess.htm Microsoft Explains Site Access Issues On Tuesday evening and Wednesday, many Microsoft customers had difficulty accessing the company's Web sites. The cause has been determined, and the issue is resolved. At 6:30 p.m. Tuesday (PST), a Microsoft technician made a configuration change to the routers on the edge of Microsoft's Domain Name Server network. The DNS servers are used to connect domain names with numeric IP addresses (e.g. 207.46.230.219) of the various servers and networks that make up Microsoft's Web presence. The mistaken configuration change limited communication between DNS servers on the Internet and Microsoft's DNS servers. This limited communication caused many of Microsoft's sites to be unreachable (although they were actually still operational) to a large number of customers throughout last night and today. This was an operational error, and not the result of any issue with Microsoft or third-party products nor the security of our networks. Microsoft regrets any inconvenience caused to customers due to this issue. At approximately 5 p.m. Wednesday (PST), Microsoft removed the changes to the router configuration and immediately saw a massive improvement in the DNS network. All sites are currently available to customers. Again, Microsoft apologizes for the inconvenience. -- Eric A. Hall http://www.ehsco.com/ Internet Core Protocols http://www.oreilly.com/catalog/coreprot/
On Wed, 24 Jan 2001, Eric A. Hall wrote:
At 6:30 p.m. Tuesday (PST), a Microsoft technician made a configuration change to the routers on the edge of Microsoft's Domain Name Server network. At approximately 5 p.m. Wednesday (PST), Microsoft removed the changes to the router configuration and immediately saw a massive improvement in the DNS network.
So basically, it took microsoft 23 hours to fix a router configuration. -Dan
On Wed, Jan 24, 2001 at 08:40:19PM -0800, Dan Hollis wrote:
On Wed, 24 Jan 2001, Eric A. Hall wrote:
At 6:30 p.m. Tuesday (PST), a Microsoft technician made a configuration change to the routers on the edge of Microsoft's Domain Name Server network. At approximately 5 p.m. Wednesday (PST), Microsoft removed the changes to the router configuration and immediately saw a massive improvement in the DNS network.
So basically, it took microsoft 23 hours to fix a router configuration.
-Dan
s/router configuration/default route/ -- Omachonu Ogali missnglnk@informationwave.net http://www.informationwave.net
Hmmm... Given the symptoms I experienced, e.g., MX and SOA lookups worked but A record lookups did not, it would appear that this statement is a big fat lie. Unless MS is doing something like shunting MX and SOA records to one server and A records to another, the point of which I could not see.... Someone tell me if I'm missing something? Matthew Devney Teamsphere Interactive On Wed, 24 Jan 2001, Eric A. Hall wrote:
Date: Wed, 24 Jan 2001 20:14:09 -0800 From: Eric A. Hall <ehall@ehsco.com> To: NANOG <nanog@nanog.org> Subject: MS explains
[anybody who shows up for a job interview with a resume saying "router ops for microsoft" should be viewed warily]
http://www.microsoft.com/info/siteaccess.htm
Microsoft Explains Site Access Issues
On Tuesday evening and Wednesday, many Microsoft customers had difficulty accessing the company's Web sites. The cause has been determined, and the issue is resolved.
At 6:30 p.m. Tuesday (PST), a Microsoft technician made a configuration change to the routers on the edge of Microsoft's Domain Name Server network. The DNS servers are used to connect domain names with numeric IP addresses (e.g. 207.46.230.219) of the various servers and networks that make up Microsoft's Web presence.
The mistaken configuration change limited communication between DNS servers on the Internet and Microsoft's DNS servers. This limited communication caused many of Microsoft's sites to be unreachable (although they were actually still operational) to a large number of customers throughout last night and today.
This was an operational error, and not the result of any issue with Microsoft or third-party products nor the security of our networks. Microsoft regrets any inconvenience caused to customers due to this issue.
At approximately 5 p.m. Wednesday (PST), Microsoft removed the changes to the router configuration and immediately saw a massive improvement in the DNS network.
All sites are currently available to customers. Again, Microsoft apologizes for the inconvenience.
-- Eric A. Hall http://www.ehsco.com/ Internet Core Protocols http://www.oreilly.com/catalog/coreprot/
participants (4)
-
Dan Hollis -
Eric A. Hall -
mdevney＠teamsphere.com -
Omachonu Ogali