MSDN must be in a DNS cache somewhere then. I can't resolve MSDN against MSFT's nameserver nslookup msdn.microsoft.com 207.46.138.12 Well, now I can't resolve anything against their nameservers, as .21, .20, .12 and .11 aren't responding to me at all. -----Original Message----- From: Steve Sobol [mailto:sjsobol@NorthShoreTechnologies.net] Sent: Thursday, January 25, 2001 12:54 PM To: Chris Davis; nanog@nanog.org Subject: Re: msdn.microsoft.com still won't resolve Chris Davis wrote:

Looks like there's more to learn. Although "the routing change was backed out", msdn.microsoft.com still won't resolve.

Comes up fine for me, but I get a "This page cannot be displayed" page. I'm not using Internet Explorer, I'm using Netscape, so it's not the browser displaying it. HTTP 500.13 Server too busy DNS, however, resolved instantly. I can't do a traceroute right now, but that's probably due to the way I have the outbound filters set on my DSL router. -- Steve Sobol, BOFH, President 888.480.4NET 866.DSL.EXPRESS 216.619.2NET North Shore Technologies Corporation http://NorthShoreTechnologies.net JustTheNet/JustTheNet EXPRESS DSL (ISP Services) http://JustThe.net mailto:sjsobol@NorthShoreTechnologies.net Proud resident of Cleveland, Ohio