[Outages-discussion] [outages] Seemingly Nationwide Comcast DNS Outage

[Frank Bulk]

Some news here: https://www.phillyvoice.com/comcast-nationwide-internet-outage-2020-january-23-philadelphia/

 

Frank 

 

From: Outages <outages-bounces at outages.org> On Behalf Of Cary Wiedemann via Outages
Sent: Thursday, January 23, 2020 3:02 PM
To: Chris Cherry <cwcherry at outlook.com>
Cc: outages at outages.org
Subject: Re: [outages] Seemingly Nationwide Comcast DNS Outage

 

Just confirming this outage affected my sites from Virginia to California.  Start time was just before 2:32pm EST and resolution came around 2:54pm EST.

 

Looks like anycast routing woes.  Not good.

 

- Cary

 

 

On Thu, Jan 23, 2020 at 3:38 PM Chris Cherry via Outages <outages at outages.org <mailto:outages at outages.org> > wrote:

No issue here with my 5 Comcast Business accounts (central Indiana), although we are using OpenDNS.  The VPN tunnels are up and running between those sites.  Friends of mine who live up near Chicago who use Comcast and use the default DNS servers from them are reporting they are up and running.

 

Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986>  for Windows 10

 

From: Christopher Trudeau via Outages <mailto:outages at outages.org> 
Sent: Thursday, January 23, 2020 3:28 PM
To: outages at outages.org <mailto:outages at outages.org> 
Subject: [outages] Seemingly Nationwide Comcast DNS Outage

 

Seeing many recent reports on the interwebs regarding a “nationwide Comcast outage”.

Looks like it’s an issue with Comcast DNS (75.75.75.75 / 75.75.76.76) and not anything else, as queries to other public DNS servers (ex: 1.1.1.1 / 8.8.8.8) work just fine over my Comcast service.

 

For reference, I’m located in Chicago, but I did perform NSLookup’s from a box in NYC, Dallas, and Seattle which resulted in similar behavior as seen below.

 

nslookup google.com <http://google.com>  75.75.75.75

Server:  UnKnown

Address:  75.75.75.75

*** UnKnown can't find google.com <http://google.com> : Query refused

 

nslookup google.com <http://google.com>  75.75.76.76

Server:  UnKnown

Address:  75.75.76.76

*** UnKnown can't find google.com <http://google.com> : Query refused

 

nslookup google.com <http://google.com>  1.1.1.1

Server:  one.one.one.one

Address:  1.1.1.1

 

Non-authoritative answer:

Name:    google.com <http://google.com> 

Addresses:  2607:f8b0:4009:812::200e

          172.217.5.14

 

nslookup google.com <http://google.com>  8.8.8.8

Server:  dns.google

Address:  8.8.8.8

 

Non-authoritative answer:

Name:    google.com <http://google.com> 

Addresses:  2607:f8b0:4009:80f::200e

          216.58.192.238

 

 




CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error please notify the sender immediately by replying to this e-mail. You must destroy the original transmission and its attachments without reading or saving in any manner. Thank you.

 

_______________________________________________
Outages mailing list
Outages at outages.org <mailto:Outages at outages.org> 
https://puck.nether.net/mailman/listinfo/outages

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages-discussion/attachments/20200123/696c6449/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 160 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/outages-discussion/attachments/20200123/696c6449/attachment-0001.png>