[33975] in North American Network Operators' Group
Re: MS explains
daemon@ATHENA.MIT.EDU (mdevney@teamsphere.com)
Thu Jan 25 20:35:57 2001
Date: Thu, 25 Jan 2001 17:33:25 -0800 (PST)
From: <mdevney@teamsphere.com>
Cc: NANOG <nanog@nanog.org>
In-Reply-To: <3A6FA810.B2EBBF5B@ehsco.com>
Message-ID: <Pine.LNX.4.21.0101251731100.7214-100000@core.teamplay.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
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/
>
