Re: Name server problems? or did Microsoft forget to pay their bill again?

[John Payne <john () sackheads org>]

On Tue, Jan 23, 2001 at 11:05:48PM -0800, Sean Donelan wrote:
> It seems like a number of Microsoft related web sites have vanished.

Seems to be Microsoft server problems...

> www.msnbc.com

$ dig msnbc.com @a.root-servers.net

;; AUTHORITY SECTION:
msnbc.com.              2D IN NS        DNS4.CP.MSFT.NET.
msnbc.com.              2D IN NS        DNS5.CP.MSFT.NET.

;; ADDITIONAL SECTION:
DNS4.CP.MSFT.NET.       2D IN A         207.46.138.11
DNS5.CP.MSFT.NET.       2D IN A         207.46.138.12

Hmmmm

$ dig www.msnbc.com @207.46.138.11
;; res options: init recurs defnam dnsrch
;; res_nsend to server 207.46.138.11: Connection timed out

$ dig www.msnbc.com @207.46.138.12
;; ANSWER SECTION:
www.msnbc.com.          1H IN CNAME     msnbc.com.
msnbc.com.              1H IN A         207.46.150.254
msnbc.com.              1H IN A         207.46.238.109
msnbc.com.              1H IN A         207.46.238.23
msnbc.com.              1H IN A         207.46.238.24
msnbc.com.              1H IN A         207.46.238.26
msnbc.com.              1H IN A         207.46.150.205


> www.microsoft.com

$ dig microsoft.com @a.root-servers.net
;; AUTHORITY SECTION:
microsoft.com.          2D IN NS        DNS4.CP.MSFT.NET.
microsoft.com.          2D IN NS        DNS5.CP.MSFT.NET.
microsoft.com.          2D IN NS        DNS7.CP.MSFT.NET.
microsoft.com.          2D IN NS        DNS6.CP.MSFT.NET.

;; ADDITIONAL SECTION:
DNS4.CP.MSFT.NET.       2D IN A         207.46.138.11
DNS5.CP.MSFT.NET.       2D IN A         207.46.138.12
DNS7.CP.MSFT.NET.       2D IN A         207.46.138.21
DNS6.CP.MSFT.NET.       2D IN A         207.46.138.20

$ dig www.microsoft.com @207.46.138.11
;; res_nsend to server 207.46.138.11: Connection timed out

$ dig www.microsoft.com @207.46.138.12
;; res_nsend to server 207.46.138.12: Connection timed out

$ dig www.microsoft.com @207.46.138.21
;; res_nsend to server 207.46.138.21: Connection timed out

$ dig www.microsoft.com @207.46.138.20
;; res_nsend to server 207.46.138.20: Connection timed out

> I've tried from both AT&T and Earthlink, and can't reach them.
>
> The name servers don't seem to be returning valid answers.  If they
> are in your cache, it works.  But after clearing the cache, nada.
>
> I noticed name server problems earlier this evening.  Is this spreading?

-- 
John Payne      http://www.sackheads.org/jpayne/    john () sackheads org
http://www.sackheads.org/uce/                    Fax: +44 870 0547954
        To send me mail, use the address in the From: header