 xfezz2 join:2005-12-13 Mokena, IL | Problems loading google (DNS issues possibly?) Well this just started happening a few days ago. All other web pages would load, except google. So my first thought was to run a full virus scan and check for spyware to make sure nothing was infected or hijacked. Both clean. Then I went to check my host file. That too is clean. 
Well I "yahooed" and came across a gentleman that was running into the same problem as I am. He too is using Comcast as his ISP and he knew of other people that were having a similar issue as well. In order for him to get google loading again he had to unplug his router and power cycle his modem.
So I thought what the heck I'll try it. And well what do you know it works. But after a day or so I'd run into the same problem and I'd have to reset my modem and router again.
I was just wondering if anyone else is having the same issue or what may be causing it? |
|
 | Yes, Im having the same problem here also. It works for a while and then turns off. I know it has nothing to do with my computer, as it does this with a clean Windows XP install, and also a clean Linux install. So, it can't be adware/virus related.
Maybe its Comcast being Comcastic. |
|
 jaminus join:2004-10-14 Arlington, VA | reply to xfezz2 I've had the same problem from time to time over the past few weeks. I think its just Comcast being Comcastic. |
|
 NormanSPremium,MVM join:2001-02-14 San Jose, CA kudos:9 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| said by jaminus:I've had the same problem from time to time over the past few weeks. I think its just Comcast being Comcastic. I suspect it is more likely Google. espaeth has already explained it in another Comcast thread on Google difficulties.
»[Connectivity] Google blocked or down!? -- Norman ~Oh Lord, why have you come ~To Konnyu, with the Lion and the Drum |
|
 andyrossPremium,MVM join:2003-05-04 Schaumburg, IL | reply to xfezz2 This is affecting many people with many different ISP's. There have been posts from AT&T DSL and others with similar issues. Sometimes, altering wireless connections and some forms of wireless security make it work. |
|
 | reply to xfezz2 For the last few weeks around 8-10PM, google.com, www.google.com, images.google.com, and maps.google.com will not load for a few hours.
But, video.google.com & news.google.com and everything else work. |
|
 | reply to xfezz2 Iv'e been having the same problem, but its not only affecting google, its also affecting Limewire |
|
|
|
 c33v33 join:2003-10-14 Chicago, IL | reply to xfezz2 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. |
|
 | reply to xfezz2 I've encountered this problem with google and several other sites when I select them from the drop down for the address bar in Internet Explorer. However, once I press enter key the page appears almost imediately. |
|
 EnasYorlThieves World join:2001-12-02 West 1 edit | reply to xfezz2 said by xfezz2:Well this just started happening a few days ago. All other web pages would load, except google. So my first thought was to run a full virus scan and check for spyware to make sure nothing was infected or hijacked. Both clean. Then I went to check my host file. That too is clean.  Well I "yahooed" and came across a gentleman that was running into the same problem as I am. He too is using Comcast as his ISP and he knew of other people that were having a similar issue as well. In order for him to get google loading again he had to unplug his router and power cycle his modem. So I thought what the heck I'll try it. And well what do you know it works. But after a day or so I'd run into the same problem and I'd have to reset my modem and router again. I was just wondering if anyone else is having the same issue or what may be causing it? »www.opendns.org :P |
|
 espaethDigital PlumberPremium,MVM join:2001-04-21 Minneapolis, MN kudos:2 Reviews:
·Vitelity VOIP
| reply to c33v33 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. |
|
 | reply to xfezz2 Seems to be a rash of sites having dns issues on the various forums I visit.  |
|
 | reply to xfezz2 I encountered this problem today with another ISP besides Comcast. |
|
 | reply to xfezz2 I have this problem every night on my Comcast connection. Every other site works including mail.google.com, but nothing that is www.google.com/. It only happens in the evening. It works fine during the day all day every day. It seems odd that it would only not work at night?
Has Comcast posted anything about it? |
|
 sortofageekNot TroublePremium,Mod join:2001-08-19 There & Then kudos:14 Host: Comcast HSI Comcast Cable TV Team Helix Distributed Comput.. Linksys
1 edit | reply to xfezz2 See also:
»google down? »Comcast blocking google? »[Connectivity] Google problems? »[Connectivity] No access to google.com from a certain comcas
-- Join Team Helix * I am praying for these friends . |
|
 | reply to xfezz2 This problem is with Google's DNS Registration. gmail works but google.com cant resolve, IPs. It's been on going for some time now, rumor around is that they had a some hardware get cracked and routing tables rewritten causing major outages. |
|
 pokesphIt Is Almost FastPremium join:2001-06-25 Sacramento, CA kudos:1 | reply to xfezz2 once again can't load google or gmail.. this time looks like level3's the issue..
C:\PPN>tracert mail.google.com
Tracing route to mail.google.com [209.85.199.83]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ppn.comcast.net [192.168.2.1]
2 36 ms 10 ms 7 ms 73.74.8.1
3 11 ms 39 ms * ge-5-10-ur01.sacramento.ca.sacra.comcast.net [68
.87.212.213]
4 6 ms * 40 ms 68.87.212.9
5 * 13 ms 15 ms te0-7-0-0-ar01.oakland.ca.sfba.comcast.net [68.8
6.90.138]
6 14 ms 45 ms 14 ms 68.86.85.77
7 16 ms 47 ms 17 ms COMCAST-IP.car2.SanJose1.Level3.net [4.79.43.134
]
8 15 ms 17 ms 47 ms te-4-4.car2.SanJose1.Level3.net [4.79.43.133]
9 57 ms 17 ms 17 ms vlan99.csw4.SanJose1.Level3.net [4.68.18.254]
10 60 ms 18 ms 4294967283 ms ae-91-91.ebr1.SanJose1.Level3.net [4.69.13
4.205]
11 40 ms 35 ms 36 ms ae-3.ebr1.Seattle1.Level3.net [4.69.132.50]
12 33 ms 33 ms 64 ms ae-11-55.car1.Seattle1.Level3.net [4.68.105.130]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 48 ms 44 ms 12 ms rv-in-f83.google.com [209.85.199.83]
Trace complete.
very annoying..
-- Webmaster - Steve - - - - - - - - - - - - »ppnhosting.com »www.1-gb.net »pokemonpalace.net |
|
 EGThe wings of lovePremium join:2006-11-18 Union, NJ kudos:9 | said by pokesph:once again can't load google or gmail.. this time looks like level3's the issue.. C:\PPN>tracert mail.google.com
Tracing route to mail.google.com [209.85.199.83]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ppn.comcast.net [192.168.2.1]
2 36 ms 10 ms 7 ms 73.74.8.1
3 11 ms 39 ms * ge-5-10-ur01.sacramento.ca.sacra.comcast.net [68
.87.212.213]
4 6 ms * 40 ms 68.87.212.9
5 * 13 ms 15 ms te0-7-0-0-ar01.oakland.ca.sfba.comcast.net [68.8
6.90.138]
6 14 ms 45 ms 14 ms 68.86.85.77
7 16 ms 47 ms 17 ms COMCAST-IP.car2.SanJose1.Level3.net [4.79.43.134
]
8 15 ms 17 ms 47 ms te-4-4.car2.SanJose1.Level3.net [4.79.43.133]
9 57 ms 17 ms 17 ms vlan99.csw4.SanJose1.Level3.net [4.68.18.254]
10 60 ms 18 ms 4294967283 ms ae-91-91.ebr1.SanJose1.Level3.net [4.69.13
4.205]
11 40 ms 35 ms 36 ms ae-3.ebr1.Seattle1.Level3.net [4.69.132.50]
12 33 ms 33 ms 64 ms ae-11-55.car1.Seattle1.Level3.net [4.68.105.130]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 48 ms 44 ms 12 ms rv-in-f83.google.com [209.85.199.83]
Trace complete.
very annoying.. What issue does that trace reveal ?
The destination server was reached. |
|
 | reply to xfezz2 I am having the same problem....  |
|