If Microsoft's problem was with routing to their DNS network, why did MX records resolve just fine? I'm afraid I don't understand that part. Is there policy routing or load balancing or something that can route MX requests to one set of dns servers while routing host requests to another set of DNS servers? As far as I can tell today, responses to my requests of the same DNS server for host records and MX records are returning from the same IP, 207.46.138.11, so it doesn't appear to me that different DNS servers are responding to different types of requests. -----Original Message----- From: Omachonu Ogali [mailto:missnglnk@informationwave.net] Sent: Thursday, January 25, 2001 8:25 AM To: Dan Hollis Cc: nanog@nanog.org Subject: Re: MS explains 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
the router configuration and immediately saw a massive improvement in
to 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
On Thu, Jan 25, 2001 at 08:47:12AM -0500, Chris Davis wrote:
If Microsoft's problem was with routing to their DNS network, why did MX records resolve just fine? I'm afraid I don't understand that part.
I was wondering that as well. Oh, and it seems to have happened again... I'm getting timeouts for microsoft.com and msnbc.com as yesterday. Although one box that has it cached has a 54 minute TTL, so I'm guessing it happened recently. -- John Payne http://www.sackheads.org/jpayne/ john@sackheads.org http://www.sackheads.org/uce/ Fax: +44 870 0547954 To send me mail, use the address in the From: header
On Thu, Jan 25, 2001 at 09:29:37AM -0800, John Payne wrote:
On Thu, Jan 25, 2001 at 08:47:12AM -0500, Chris Davis wrote:
If Microsoft's problem was with routing to their DNS network, why did MX records resolve just fine? I'm afraid I don't understand that part.
I was wondering that as well. Oh, and it seems to have happened again... I'm getting timeouts for microsoft.com and msnbc.com as yesterday. Although one box that has it cached has a 54 minute TTL, so I'm guessing it happened recently.
http://www.microsoft.com/info/siteaccess.htm has been updated. Jan 25th outage was a DoS attack. -- John Payne http://www.sackheads.org/jpayne/ john@sackheads.org http://www.sackheads.org/uce/ Fax: +44 870 0547954 To send me mail, use the address in the From: header
participants (2)
-
Chris Davis -
John Payne