Google DNS server down

395 views
Skip to first unread message

Piaw Na(藍俊彪)

unread,
Jan 30, 2010, 8:50:11 PM1/30/10
to public-dns-discuss
Did 8.8.8.8 and 8.8.4.4 start failing? I had add back comcast's DNS
servers to my router before I could ping www.google.com today.

Ancient Brit

unread,
Feb 1, 2010, 1:12:41 AM2/1/10
to public-dns-discuss
I experienced a similar problem with my router (Netgear WNR834B with
latest firmware) today. It was reproducible.

I reconfigured the router to use 8.8.8.8 and 8.8.4.4 as DNS in place
of the Time Warner/RoadRunner offerings. I've done likewise with
FreeDNS in the past until their service slowed and it was better to
switch back to TW.

The internal router test failed to connect to the Netgear KB server
used to check whether connectivity is up.

I reset to the default (ISP-provided) DNS and the connection was fine.

I went back and reconfigured for Google DNS, still failed.

I ran checks (using TW DNS) to see whether IP 8.8.8.8 was accessible,
using CLI PING in a DOS box under XP Pro (all patches current) -
result OK; using NeoTracePro (result OK); using GRC's ID Serve (result
OK, with the caveat that of course it's not set up as a Web server so
probably wouldn't respond on port 80, but the server's name was given
as google-public-dns-a.google.com, confirming what I assume is the
correct address).

Not sure why the DNS access isn't working - I'd like to try it out.
However, I'm not going to commit time and effort to a telephone query.
If I can't resolve it in email or a forum like this then I don't tend
to bother following up.

Ancient Brit

unread,
Feb 1, 2010, 2:53:12 AM2/1/10
to public-dns-discuss
My bad - not FreeDNS, OpenDNS.

> > servers to my router before I could pingwww.google.comtoday.- Hide quoted text -
>
> - Show quoted text -

Reply all
Reply to author
Forward
0 new messages