On Fri, Jan 26, 2001 at 04:59:13PM -0500, Michael H. Warfield wrote:
> No... Microsoft learned, just two days ago, something that has
> been part of best practices for over 15 years. Do NOT put all of your
> DNS servers on the same network! The technical error may have triggered
> the meltdown but if they had distributed their DNS the way they were
> suppose to, it would have NOT taken them totally out. It wasn't the
> technician's mistake. It was the single point of failure (and subsequently
> the single point of attack). He just triggered it.
Nope, they didn't learn it yet.
Although asking NS pointers from Microsoft's DNS servers shows
a set Akamai's DNS servers along with MS' ones, those must be
listed at .COM for them to become used...
whois -h whois.internic.net microsoft.com
...
Record last updated on 24-Jan-2001.
Domain servers in listed order:
DNS4.CP.MSFT.NET 207.46.138.11
DNS5.CP.MSFT.NET 207.46.138.12
DNS6.CP.MSFT.NET 207.46.138.20
DNS7.CP.MSFT.NET 207.46.138.21
> Mike
> --
> Michael H. Warfield | (770) 985-6132 | mhw@WittsEnd.com
/Matti Aarnio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jan 31 2001 - 21:00:27 EST