 espaethDigital PlumberPremium,MVM
join:2001-04-21
Minneapolis, MN
kudos:2
 ·Clear Wireless
| reply to c33v33
Re: Problems loading google (DNS issues possibly?)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 |
 tshirtPremium,MVM
join:2004-07-11
Snohomish, WA
kudos:3 | 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. |
