Microsoft Problems :-(
Barry Margolin
barmar at genuity.net
Wed Jan 24 16:55:08 UTC 2001
In article <94n15i$rp2 at pub3.rc.vix.com>, <janl at linpro.no> wrote:
>
>"Klinkefus, David S" <DSKlinkefus at midamerican.com> tastet:
>> Microsoft Web sites suffer large-scale blackout
>...
>
>I think we can disregard the "ICANN fubared" theory.
>
>microsoft.com NS DNS7.CP.MSFT.NET
>microsoft.com NS DNS6.CP.MSFT.NET
>microsoft.com NS DNS4.CP.MSFT.NET
>microsoft.com NS DNS5.CP.MSFT.NET
>
>This matches whois ("whois microsoft.com" is somewhat entertaining
>btw). Furthermore:
>
>DNS4.CP.MSFT.NET A 207.46.138.11
>DNS5.CP.MSFT.NET A 207.46.138.12
>DNS6.CP.MSFT.NET A 207.46.138.20
>DNS7.CP.MSFT.NET A 207.46.138.21
>
>Of course I don't know anything about their network topology, but
>it looks like their nameservers are located at one or perhaps two
>locations within the msft.net. Traceroute to all of them stops at
>the same place, one jump of alter.net, so they all share one point
>of failure it looks like.
>
>This does not tell us anything about what failed and how though.
There's a thread in c.p.t.domains about a DNS problem affecting Microsoft
that was due to a screwup at MyDomains.com. I think the article that
blamed them came from someplace like wired.com. The article didn't go into
much technical detail, either, but our best guess is that cache poisoning
was involved, which caused servers to use the mydomains.com servers instead
of the registered servers.
But if it's known that this is the problem, why is Microsoft blaming the
normal DNS delegation authorities?
--
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
More information about the bind-users
mailing list