msdn.microsoft.com still won't resolve
Looks like there's more to learn. Although "the routing change was backed out", msdn.microsoft.com still won't resolve. The MSDN site's there, though: http://207.46.130.161/ -----Original Message----- From: Steven M. Bellovin [mailto:smb@research.att.com] Sent: Thursday, January 25, 2001 11:54 AM To: Randy Bush Cc: Dan Hollis; Eric A. Hall; NANOG Subject: Re: MS explains In message <E14LpXc-0000ET-00@roam.psg.com>, Randy Bush writes:
I'd love to see a detailed description of what went wrong, and I hope that those in the know will be allowed to post it or present it in Atlanta.
was it not don knuth's turing aware lecture which consisted of a detailed analysys of some recent bugs in his code?
We all learn much more from failures than from successes. To quote Alfred E. Neuman, "Learn from the mistakes of others; you'll never live long enough to make them all yourself." --Steve Bellovin, http://www.research.att.com/~smb
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
----- Original Message ----- From: "Steve Sobol" <sjsobol@NorthShoreTechnologies.net> To: "Chris Davis" <chris.davis@computerjobs.com>; <nanog@nanog.org> Sent: Thursday, January 25, 2001 6:53 PM 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. 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.
nslookup:
www.microsoft.com Server: DNS6.CP.MSFT.NET Address: 207.46.138.20
*** DNS6.CP.MSFT.NET can't find www.microsoft.com: No response from server traceroute: Type escape sequence to abort. Tracing the route to DNS6.CP.MSFT.NET (207.46.138.20) 1 fe8-0-0.san-bb1.cerf.net (134.24.38.225) [AS 1740] 0 msec 0 msec 0 msec 2 pos0-0-155M.san-bb6.cerf.net (134.24.29.130) [AS 1740] 0 msec 4 msec 0 msec 3 ge6-3-0.san-bb4.cerf.net (134.24.29.149) [AS 1740] 0 msec 4 msec 0 msec 4 pos3-0-622M.lax-bb5.cerf.net (134.24.29.14) [AS 1740] 4 msec 4 msec 4 msec 5 pos5-0-622M.lax-bb4.cerf.net (134.24.33.169) [AS 1740] 8 msec 4 msec 8 msec 6 cerfnet-gw.la6ca.ip.att.net (192.205.32.109) [AS 7018] 4 msec 8 msec 4 msec 7 gbr3-p40.la2ca.ip.att.net (12.123.132.6) [AS 7018] 8 msec 4 msec 4 msec 8 gbr4-p90.sffca.ip.att.net (12.122.2.170) [AS 7018] 16 msec 12 msec 12 msec 9 gbr3-p50.st6wa.ip.att.net (12.122.2.62) [AS 7018] 28 msec 28 msec 28 msec 10 gbr1-p100.st6wa.ip.att.net (12.122.5.158) [AS 7018] 28 msec 32 msec 28 msec 11 gar1-p360.st6wa.ip.att.net (12.123.44.58) [AS 7018] 32 msec 28 msec 32 msec 12 12.127.79.58 [AS 7018] 44 msec 48 msec 36 msec 13 * * * It looks like dns servers are down again... Karel Chvalovsky (LUPA.CZ)
On Thu, 25 Jan 2001, Karel Chvalovsky wrote:
It looks like dns servers are down again...
Uh. same router-misconfiguration as yesterday :-) Starts making me laugh. cu Clemens. -- /"\ / The race to maintain an up-to-date \ / ASCII RIBBON CAMPAIGN / system is long and, in the end, it's X AGAINST HTML MAIL / only with yourself. / \ AND POSTINGS / (Ben@lspace.org)
participants (4)
-
Chris Davis -
Clemens Zauner -
Karel Chvalovsky -
Steve Sobol