- NANOG - lists.nanog.org

RE: Microsoft spokesperson blames ICANN
by Roeland Meyer 25 Jan '01

25 Jan '01

Blaming it on ICANN, even indirectly, is about as clueless a move as can be imagined. ICANN has no direct authority over the root, the USG/DOC/NTIA has reserved that privilege for itself alone. They have let out the operations contract to NSI, who manages the a.root-servers.net and has been doing so for years. MHSC has been working with MS engineering and support staff, for the past few months, to integrate BIND8.2.2p7 servers with Win2K/DNS/AD. It isn't easy because of semantic inconsistency, radically diverse architecture concepts, and [above all] severe lack of documentation on MS part (as well as a few roaches in the SRV update stuff). >From our efforts, it is not at all surprising that someone, at MSFT, munged the DNS configuration, totally. Even their best guru could have done it, due to the murky nature of the config. I suspect that there are less than 100 ppl that could even have a clue, in this area, and they don't all have the same pieces of clue. Win2K DNS is self-consistent, BIND is self-consistent, they may be mutually consistent, but that has yet to be determined. MSFT works in a glasshouse with many of the panes painted-over, others are distorted. Similary, there is a tendency, among *nix folk, to discount anything MSFT (a mistake, IMHO). What's needed is for some(one/group) that has a though understanding of both systems, at the design level, to sort out the bits. This is properly, a development project, one that most system admins are unsuited for. Unfortunately, it is left at the system admin level, IMHO. -- ROELAND M.J. MEYER Managing Director Morgan Hill Software Company, Inc. TEL: +001 925 373 3954 FAX: +001 925 373 9781 http://www.mhsc.com mailto: rmeyer(a)mhsc.com > -----Original Message----- > From: Sean Donelan [mailto:sean@donelan.com] > Sent: Wednesday, January 24, 2001 11:40 AM > To: nanog(a)merit.edu > Subject: Microsoft spokesperson blames ICANN > > > > Microsoft appears to be blaming ICANN for the failure with Microft's > domain name servers (all located at the same place at Microsoft). > > Microsoft has yet to pin down the cause of the DNS error. "It can > be a system or human error, but somebody could also have done this > intentionally," De Jonge said. "We don't manage the DNS ourselves, > it is a system controlled by the Internet Corporation for Assigned > Names and Numbers (ICANN) with worldwide replicas." > > http://www.idg.net/ic_386962_1793_1-1681.html > > Microsoft gamers (users of www.zone.com) quickly came up with various > workarounds so they could continue playing. They were > posting HOSTS.TXT > files on various gamer bulletin boards overnight. In particular > "Asheron's Call" had several problems during the last week, including > banning a number of users and rolling back experience points due to > a game bug.

5 6

Re: Microsoft spokesperson blames ICANN
by Richard A. Steenbergen 25 Jan '01

25 Jan '01

On Wed, Jan 24, 2001 at 08:30:12PM -0500, Henry Yen wrote: > > try: http://secondary.easydns.com Super-redundant DNS hosting would make a good product. Akamai maybe? -- Richard A Steenbergen <ras(a)e-gerbil.net> http://www.e-gerbil.net/ras PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6)

9 8

Tenure (was Re: MS explains)
by Sean Donelan 25 Jan '01

25 Jan '01

On Thu, 25 January 2001, "Steven M. Bellovin" wrote: > In message <E14LpXc-0000ET-00(a)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." Donald Knuth has tenure. He can give all the lectures he wants about his greatest mistakes. Although all the "experts" say honesty is the best policy, the PR people at publically traded companies feel less is more. When the net was mostly operated and managed by academics, there was a reward in publishing the resultes of your mistakes. In today's net, you are likely to be punished or fired for publically discussing what happened. Ebay has never publically explained what went wrong with their equipment, Abovenet has never publically explained what went wrong with their router configuration, Worldcom has never publically explained what went wrong with their switches. Juniper and Cisco have been trading router interoperability bugs for a while, but they aren't publically discussed. Sometimes you might get a little information under NDA, but publish a "white paper?" Never! Admitly, there are exceptions. AT&T did release a fairly detailed analysis when they lost most of their 5ESSs switches due to a software bug. But it is so rare, we remember them because they are so rare.

1 0

RE: OUTAGE: Earthlink - more nationwide difficulties
by Roeland Meyer 25 Jan '01

25 Jan '01

Oh yeah, they blamed it on PAIX. > -----Original Message----- > From: Roeland Meyer > Sent: Thursday, January 25, 2001 11:00 AM > To: 'Sean Donelan'; nanog(a)merit.edu > Subject: RE: OUTAGE: Earthlink - more nationwide difficulties > > > DSLnetworks (my lvrmr upstream) had outage (redback router) > from 2300 til 0900 this morning.<sheesh!> > > Can we say "PO'd moi"! > > > -----Original Message----- > > From: Sean Donelan [mailto:sean@donelan.com] > > Sent: Thursday, January 25, 2001 10:49 AM > > To: nanog(a)merit.edu > > Subject: OUTAGE: Earthlink - more nationwide difficulties > > > > > > > > Earthlink appears to have either a new, or continuing > routing problem > > affecting much of their network. > > > > > > >

1 0

RE: OUTAGE: Earthlink - more nationwide difficulties
by Roeland Meyer 25 Jan '01

25 Jan '01

DSLnetworks (my lvrmr upstream) had outage (redback router) from 2300 til 0900 this morning.<sheesh!> Can we say "PO'd moi"! > -----Original Message----- > From: Sean Donelan [mailto:sean@donelan.com] > Sent: Thursday, January 25, 2001 10:49 AM > To: nanog(a)merit.edu > Subject: OUTAGE: Earthlink - more nationwide difficulties > > > > Earthlink appears to have either a new, or continuing routing problem > affecting much of their network. > > >

1 0

OUTAGE: Qwest - problem?
by Sean Donelan 25 Jan '01

25 Jan '01

Qwest also seems to be having widespread difficulties. Is there something common going on? I haven't heard of any fiber cuts.

1 0

OUTAGE: Earthlink - more nationwide difficulties
by Sean Donelan 25 Jan '01

25 Jan '01

Earthlink appears to have either a new, or continuing routing problem affecting much of their network.

1 0

Re: CAIS DSL failure: lessons in how not to inform
by Steve Sobol 25 Jan '01

25 Jan '01

John Todd wrote: > When I'm on hold with a vendor and I get music (or worse, ads) pumped > into my ear, I will often ask for the manager on the next opportunity > that someone comes on the line. I'm exactly the opposite. I don't necessarily want to hear ads, but I don't like not quite being sure whether I'm connected or not :) -- 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

2 1

msdn.microsoft.com still won't resolve
by Chris Davis 25 Jan '01

25 Jan '01

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(a)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

4 3

RE: msdn.microsoft.com still won't resolve
by Chris Davis 25 Jan '01

25 Jan '01

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(a)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

1 0