Welcome to Comcast Help & Support Forums
Find solutions, share knowledge, and get answers from customers and experts

New to the Community? Start here.

5,636,064

members

66

online now

1,813,908

discussions

Back to Top

Re: Weather.Gov DNS

SOLVED
Posted by
Visitor
  • Thank you contributor for your first reply to the community!
 Posting replies is the best way to get involved.
  • Congrats on Posting your first topic!

Message 2 of 19
2,574 Views

i can confirm that only weather.gov is down only with comcast.  I've checked with others not using comcast and they are up and running.

18 REPLIES
Posted by
Silver Problem Solver

Message 1 of 19
2,587 Views

Weather.gov and noaa.gov are not accessible again...

 

The Comcast DNS cache check shows only Denver returning an address.

Posted by
Visitor
  • Thank you contributor for your first reply to the community!
 Posting replies is the best way to get involved.
  • Congrats on Posting your first topic!

Message 3 of 19
2,569 Views

i did a quick search to figure out how to change my dns server to google... I switched it and weather.gov is running perfectly.  I'm soooo dissapointed with comcast.  TV and Internet.

Posted by
Contributor

Message 4 of 19
2,555 Views

Not working here also, though I use noaa.gov as my URL.  Changed to the public DNS 8.8.8.8.8, and it works.

Posted by
Problem Solver

Message 5 of 19
2,541 Views

For those of you experiencing issues with weather.gov and noaa.gov, can you please post traceroute and pings to those sites?  Can you please also confirm what DNS server you are pointing to when running traceroute and ping?

 

We could really use your help providing this data so we can troubelshoot further. If you have any additional questions, please PM me.

 

Thanks

Chris

Comcast

 

 

Posted by
Gold Problem Solver

Message 6 of 19
2,513 Views

ctg1701a wrote: ... can you please post traceroute and pings to those sites? ...

If you'll explain how to run ping and traceroute for a host which DNS cannot resolve, I'd be happy to help.

 

Meanwhile:

 

  nslookup Weather.gov 75.75.75.75  (Comcast)
  Server:  cdns01.comcast.net
  Address:  75.75.75.75
  *** cdns01.comcast.net can't find Weather.gov: Server failed

  nslookup Weather.gov 8.8.4.4  (Google)
  Address:  204.227.127.201

  nslookup Weather.gov 4.2.2.1  (Verizon)
  Address:  204.227.127.201

  nslookup Weather.gov 208.67.220.220  (OpenDNS)
  Address:  204.227.127.201

 

I'm in York PA, 17401.

 

This post might be relevant: http://forums.comcast.com/t5/Connectivity-and-Modem-Help/NASA-gov-blocked/m-p/1170279#M146392

Posted by
Problem Solver

Message 7 of 19
2,508 Views

BruceW wrote:

ctg1701a wrote: ... can you please post traceroute and pings to those sites? ...

If you'll explain how to run ping and traceroute for a host which DNS cannot resolve, I'd be happy to help.

 

Meanwhile:

 

  nslookup Weather.gov 75.75.75.75  (Comcast)
  Server:  cdns01.comcast.net
  Address:  75.75.75.75
  *** cdns01.comcast.net can't find Weather.gov: Server failed

  nslookup Weather.gov 8.8.4.4  (Google)
  Address:  204.227.127.201

  nslookup Weather.gov 4.2.2.1  (Verizon)
  Address:  204.227.127.201

  nslookup Weather.gov 208.67.220.220  (OpenDNS)
  Address:  204.227.127.201

 

I'm in York PA, 17401.


Can you please run a traceroute to 75.75.75.75 from your location?  This will show us which resolver you location you are pointed to.

 

Thanks

Chris

Comcast

Posted by
Gold Problem Solver

Message 8 of 19
2,505 Views

ctg1701a wrote: ... Can you please run a traceroute to 75.75.75.75 from your location? ...

C>tracert 75.75.75.75

Tracing route to cdns01.comcast.net [75.75.75.75] over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router [192.168.1.1]
  2    36 ms    30 ms    29 ms  174.49.192.1
  3    11 ms     9 ms     9 ms  te-0-7-0-2-sur01.york.pa.pitt.comcast.net [68.85.43.241]
  4    12 ms    11 ms    11 ms  te-0-12-0-2-ar03.lowerpaxton.pa.pitt.comcast.net [69.139.194.57]
  5    23 ms    22 ms    19 ms  te-0-7-0-1-ar03.pittsburgh.pa.pitt.comcast.net [69.139.194.214]
  6    31 ms    38 ms    32 ms  pos-4-14-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.94.185]
  7    35 ms    35 ms    35 ms  pos-2-14-0-0-ar01.needham.ma.boston.comcast.net [68.86.93.34]
  8    36 ms    35 ms    35 ms  te-4-1-ur01.chelmsfdrdc2.ma.boston.comcast.net [68.87.145.230]
  9     *       37 ms    35 ms  cdns01.comcast.net [75.75.75.75]

Trace complete.

Posted by
Official Employee

Message 9 of 19
2,493 Views

It kind of looks like a bunch of .gov domains had a key rollover problem. We're investigating.

 

Chris

Posted by
Problem Solver

Message 10 of 19
2,540 Views
Solution

BruceW wrote:

ctg1701a wrote: ... Can you please run a traceroute to 75.75.75.75 from your location? ...

C>tracert 75.75.75.75

Tracing route to cdns01.comcast.net [75.75.75.75] over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router [192.168.1.1]
  2    36 ms    30 ms    29 ms  174.49.192.1
  3    11 ms     9 ms     9 ms  te-0-7-0-2-sur01.york.pa.pitt.comcast.net [68.85.43.241]
  4    12 ms    11 ms    11 ms  te-0-12-0-2-ar03.lowerpaxton.pa.pitt.comcast.net [69.139.194.57]
  5    23 ms    22 ms    19 ms  te-0-7-0-1-ar03.pittsburgh.pa.pitt.comcast.net [69.139.194.214]
  6    31 ms    38 ms    32 ms  pos-4-14-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.94.185]
  7    35 ms    35 ms    35 ms  pos-2-14-0-0-ar01.needham.ma.boston.comcast.net [68.86.93.34]
  8    36 ms    35 ms    35 ms  te-4-1-ur01.chelmsfdrdc2.ma.boston.comcast.net [68.87.145.230]
  9     *       37 ms    35 ms  cdns01.comcast.net [75.75.75.75]

Trace complete.


Can you please retry your DNS lookup now?  It seems there was a key rollover for DNSSEC for .gov domains and we had cached entries that had not timed out for the old keys.

 

Thanks

Posted by
Visitor
  • Thank you contributor for your first reply to the community!
 Posting replies is the best way to get involved.

Message 11 of 19
2,485 Views

Umm I just wanted to report Atlanta Ga wouldn't connect to noaa.gov or weather.gov.  but it has just started working now. 

Posted by
Gold Problem Solver

Message 12 of 19
2,480 Views

ctg1701a wrote: ... Can you please retry your DNS lookup now? ...

   nslookup Weather.gov 75.75.75.75  (Comcast)
   Server:  cdns01.comcast.net
   Address:  75.75.75.75

   Non-authoritative answer:
   Name:    Weather.gov
   Address:  204.227.127.201

 

All better for me -- Noaa.gov is OK too.

 

Posted by
Contributor

Message 13 of 19
2,443 Views

Seems to be OK here now too.  Thanks!

Posted by
Official Employee

Message 14 of 19
2,427 Views

I hope to be able to work with the team to do a detailed analysis of what happened. We just completed something similar for NASA.GOV. See http://www.dnssec.comcast.net/DNSSEC_Validation_Failure_NASAGOV_20120118_FINAL.pdf

JL
Internet Services


Community Icon
I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: Product, Support, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.

Was your question answered? Mark it as an accepted solution!solution Icon
Community Icon
I am an Offical Comcast Employee.
Official Employees are from multiple teams within Comcast.
We ask that you post publicly so people with similar questions may benefit.
Was your question answered? Mark it as an accepted solution!solution Icon
Community Icon
I am a Comcast Employee.
Please post so people with similar questions may benefit.
Was your question answered?
Mark it as a solution!solution Icon
Posted by
Regular Visitor
  • Thank you contributor for your first reply to the community!
 Posting replies is the best way to get involved.
  • Congrats on Posting your first topic!
  • Congratulations on receiving your first Kudos! Thank you for your meaningful contribution to the forum. May this be the first of many kudos.

Message 15 of 19
2,393 Views

Can the powers that be allow dig +dnssec +trace output much like you allow querying of your nameservers via a web page?  It is hard to debug when at work without access to the Comcast DNS servers.

Posted by
Frequent Visitor
  • You have posted 5 replies to the community. Thank you for keeping the conversations going!
  • Thank you contributor for your first reply to the community!
 Posting replies is the best way to get involved.
  • Congrats on Posting your first topic!

Message 16 of 19
2,362 Views

Having the same problem in Philadelphia area..   My Nexrad Radar software stopped working, and traced the problem to not being able to access Noaa.gov and  weather.gov

Posted by
Gold Problem Solver

Message 17 of 19
2,359 Views

Looks like the Feds have messed up their DNSSEC again. Comcast correctly resolves "noaa.gov", but HTTP requests to "noaa.gov" are redirected to "www.noaa.gov", which does not resolve correctly. See http://dnsviz.net/d/www.noaa.gov/dnssec/.

Posted by
Regular Visitor
  • Thank you contributor for your first reply to the community!
 Posting replies is the best way to get involved.
  • Congrats on Posting your first topic!
  • Congratulations on receiving your first Kudos! Thank you for your meaningful contribution to the forum. May this be the first of many kudos.

Message 18 of 19
2,305 Views

BTW, we looked at this a bit, for www.noaa.gov.

 

The visual tool has an option to refresh all the data.  The default uses some cached keys, which

can give some warnings.  Once we used the refreshed data, it looked correct.

-

Posted by
Connection Expert

Message 19 of 19
737 Views