dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
91
c33v33
join:2003-10-14
Chicago, IL

c33v33 to xfezz2

Member

to xfezz2

Re: Problems loading google (DNS issues possibly?)

Same problem. Started a few days ago.

I'm guessing Comcast DNS issues. »64.233.187.99 works for google, but not »www.google.com.

I notice this happens at night for me. Google works during the afternoons. Not sure why.

SpaethCo
Digital Plumber
MVM
join:2001-04-21
Minneapolis, MN

SpaethCo

MVM

This could be a problem with Comcast DNS if they are caching records longer than Google's advertised TTL. Using Comcast's DNS servers, can you run "nslookup" and do the following:

> set debug
> www.google.com

The output at the end should have something that looks like this:
    QUESTIONS:
        www.google.com, type = A, class = IN
    ANSWERS:
    ->  www.google.com
        canonical name = www.l.google.com
        ttl = 82165 (22 hours 49 mins 25 secs)
    ->  www.l.google.com
        internet address = 64.233.167.147
        ttl = 238 (3 mins 58 secs)
    ->  www.l.google.com
        internet address = 64.233.167.99
        ttl = 238 (3 mins 58 secs)
    ->  www.l.google.com
        internet address = 64.233.167.104
        ttl = 238 (3 mins 58 secs)
 

What do you get back for TTL values when it's not working? Google has their www.l.google.com records set to a 300 second (5 min) time to live (ttl), so if you see a number bigger than that in the addresses that resolve for www.l.google.com you could very well have a DNS issue.

-Eric

tshirt
Premium Member
join:2004-07-11
Snohomish, WA

tshirt

Premium Member

google has verified it was a DNS error (or hack? or problem with the Web Accelerator Beta?) that then spread to other ISP's DNS.
Since many who didn't get google.com but instead got google.corn.net a hack seems likely.