Topic 'Re: Problems loading google (DNS issues possibly?)' in forum 'Comcast HSI' - dslreports.com

Re: Problems loading google (DNS issues possibly?)

Thu, 01 Nov 2007 11:53:15 EDT

espaeth posted : ATT and Sonic.net have been reported here.

»Can't access Google domains.
»Can't access google.com?

Re: Problems loading google (DNS issues possibly?)

Thu, 01 Nov 2007 11:43:42 EDT

scottwed posted : Just curious, does anyone have a list of other ISPs with the same issue?

I'm also perplexed as to how Hamachi is also having the same issue (the packet traces are identical in regards to the odd resets).

For the record, I haven't had the issue for 3 days now, but I've also scheduled any significant traffic to occur after midnight.

Re: Problems loading google (DNS issues possibly?)

Wed, 31 Oct 2007 21:55:42 EDT

espaeth posted :

said by Nubiatech:

Although the ttl's suggest the resets are coming from further up (ttl 51 = 13 hops), it is not necessarily so. TTLs could easily be manipulated or setup to suggest just that.

Agreed. All things being equal though, Comcast isn't the only ISP having this problem, which would also tend to suggest something closer to Google's network.

Re: Problems loading google (DNS issues possibly?)

Wed, 31 Oct 2007 19:14:51 EDT

Nubiatech posted :

said by espaeth:

said by clayjar:

Thanks, Nubiatech. That was the best detailed explanation/interpretation offered so far. Someone from Comcast needs to look into this and fix it.

Actually that analysis would tend to suggest it's something on Google's side. The resets are coming from too far out to be Comcast.

Although the ttl's suggest the resets are coming from further up (ttl 51 = 13 hops), it is not necessarily so. TTLs could easily be manipulated or setup to suggest just that.

It gets even more interesting,
Can't get to www.google.com? then try:
»google.navigation.opendns.com

This opens a new can of worms: is Comcast also trying to redirect and cache Google traffic just like OpenDNS is doing? (Ref: »forums.opendns.com/comments.php?···1#Item_0)

Re: Problems loading google (DNS issues possibly?)

Wed, 31 Oct 2007 17:34:16 EDT

espaeth posted :

said by clayjar:

Thanks, Nubiatech. That was the best detailed explanation/interpretation offered so far. Someone from Comcast needs to look into this and fix it.

Actually that analysis would tend to suggest it's something on Google's side. The resets are coming from too far out to be Comcast.

Re: Problems loading google (DNS issues possibly?)

Wed, 31 Oct 2007 16:07:59 EDT

clayjar posted : Thanks, Nubiatech. That was the best detailed explanation/interpretation offered so far. Someone from Comcast needs to look into this and fix it.

Re: Problems loading google (DNS issues possibly?)

Wed, 31 Oct 2007 11:39:43 EDT

SuperNet9 posted :

said by FromSnowLand :

I have been having the same problem for over a week. Here is what I have found:
1) it only happens between 7 pm and midnight
2) only happens if I have been downloading for over an hour (news-reader - no impact on downloads)
3) only impacts iGoogle, Google search & Google Reader (gmail & google news work fine)

Almost the same thing but my speeds drop down to 2megs
--
Comcast HSI 8.0-768 / ATT CV - VoIP / »www.TalkAboutVoIP.COM - VoIP news & help / »www.ChicagoMaximaClub.net - My Website !

Re: Problems loading google (DNS issues possibly?)

Wed, 31 Oct 2007 09:36:22 EDT

Nubiatech posted : Thanks clayjar and svideo for providing packet captures.
Here are my observations:

1. After google recieves an SYN from clayjar 's computer, it replies with SYN/ACK

17:24:50.305541 IP (tos 0x20, ttl 53, id 57627, offset 0, flags [none], proto TCP (6), length 60) py-in-f147.google.com.http > 192.168.12.3.36519: S, cksum 0x1a42 (correct), 1211513156:1211513156(0) ack 4243223793 win 5672

Pay attention to the following:
-- time to live (ttl 53) (it means google is 11 hops away, but we are not concerned about the exact number).
-- the tcp timestamp (28289791)
-- the tcp window size (win 5672). Note that OS defaults differ on this value (check dslreports.com speed tweaks faqs).

2. After the computer completes the handshake by sending an ACK and start the connection(PSH), here come the mysterious RSTs:

17:24:50.328010 IP (tos 0x0, ttl 51, id 57631, offset 0, flags [DF], proto TCP (6), length 52) py-in-f147.google.com.http > 192.168.12.3.36519: R, cksum 0x255e (correct), 1211513157:1211513157(0) win 10240 17:24:50.328113 IP (tos 0x0, ttl 51, id 57632, offset 0, flags [DF], proto TCP (6), length 52) py-in-f147.google.com.http > 192.168.12.3.36519: R, cksum 0xf486 (correct), 1211525660:1211525660(0) win 10240

Here we have a ttl 51 which indicates that these packet are not from the original source (Google). Another clue is the tcp window size (win 10240), which can not be that high without scaling after a connection is established. It is clear that this a different host sitting in the middle. Also note that the 2 RST packets were sent 0.0017 seconds in between! This is very unusual.
And tcp timestamp 28290791, although optional, but decreased!?

3.
The computer upon recieving the RST, replies with an RST and closes its side of the connection:

17:24:50.332401 IP (tos 0x20, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 40) 192.168.12.3.36519 > py-in-f147.google.com.http: R, cksum 0xf8e4 (correct), 4243224049:4243224049(0) win 0

4. And finally, ffw, Google upon recieving RSTs from the host in the middle, closes its side of the connection. Note here we confirm it is google: (ttl 53), a consistent tcp timestamp (28289791), and a low (win 6432). No need to go into window scaling discussion.

17:24:50.381396 IP (tos 0x20, ttl 53, id 57629, offset 0, flags [none], proto TCP (6), length 52) py-in-f147.google.com.http > 192.168.12.3.36519: R, cksum 0x44c9 (correct), 1:1(0) ack 257 win 6432

Conclusion: there is something out there resetting tcp connection to that ip address.

Now, the question is: how come it is possible to use the ip address directly to connect to Google?
My answer: most likely a DNS issue. It could be that at certain times of the day, Google.com DNS entries change to ip addresses that "the host in the middle" above does not like. Keep in mind that, as mentioned in this thread, that Google's DNS entries have very short TTLs:

C:\>nslookup> set debug> www.google.comServer:  UnKnownAddress:  192.168.10.1 ------------Got answer:    HEADER:        opcode = QUERY, id = 6, rcode = NXDOMAIN        header flags:  response, want recursion, recursion avail.        questions = 1,  answers = 0,  authority records = 0,  additional = 0     QUESTIONS:        www.google.com.lan, type = A, class = IN ------------------------Got answer:    HEADER:        opcode = QUERY, id = 7, rcode = NOERROR        header flags:  response, want recursion, recursion avail.        questions = 1,  answers = 3,  authority records = 0,  additional = 0     QUESTIONS:        www.google.com, type = A, class = IN    ANSWERS:    ->  www.google.com        canonical name = google.navigation.opendns.com        ttl = 8 (8 secs)    ->  google.navigation.opendns.com        internet address = 208.67.216.231        ttl = 8 (8 secs)    ->  google.navigation.opendns.com        internet address = 208.67.216.230        ttl = 8 (8 secs) ------------Non-authoritative answer:Name:    google.navigation.opendns.comAddresses:  208.67.216.231, 208.67.216.230Aliases:  www.google.com >

Re: Problems loading google (DNS issues possibly?)

Wed, 31 Oct 2007 02:17:57 EDT

anon posted : I have been having the same problem for over a week. Here is what I have found:
1) it only happens between 7 pm and midnight
2) only happens if I have been downloading for over an hour (news-reader - no impact on downloads)
3) only impacts iGoogle, Google search & Google Reader (gmail & google news work fine)

I did some testing and if I go through a HTTP Proxy service, I can access the 3 google services just fine, even though at the same time I get the connection resets directly.

I have heard the Comcast is using the Sandvine service to manage traffic, that these devices are internal to the Comcast network (not at the edge) and are responsible for the resets. I suspect that Sandvine has determined certain Google services are p2p and is issuing resets to slow them down, but since they are really web applications, they die when reset (conjecture on my part).

Re: Problems loading google (DNS issues possibly?)

Wed, 31 Oct 2007 00:07:12 EDT

clayjar posted :

said by nosprings:

Can anyone post traces showing the resets? I want to see if I was having the same problem

Here's a dump of data on port 80 on my box while trying to connect to www.google.com. Hope that helps.

dump.txt 7,628 bytes
tcpdump from port 80

Re: Problems loading google (DNS issues possibly?)

Tue, 30 Oct 2007 20:35:10 EDT

nosprings posted : Can anyone post traces showing the resets? I want to see if I was having the same problem

Re: Problems loading google (DNS issues possibly?)

Tue, 30 Oct 2007 20:00:30 EDT

nosprings posted : I would like to see the captures

Re: Problems loading google (DNS issues possibly?)

Tue, 30 Oct 2007 19:54:02 EDT

Comspastic posted : Google hasn't changed anything. He's saying it's related to root and caching servers, and it doesn't have to do with google at all. Sorry i don't know that much about DNS.

Re: Problems loading google (DNS issues possibly?)

Tue, 30 Oct 2007 13:05:12 EDT

anon posted : Not sure if this violates posting policy, but for those that are trying to debug this can you please report your findings to »www.google.com/support/bin/reque···x=answer so the members of traffic team inside Google can either pressure Comcast to fix this issue or double check the settings on Google's infrastructure to assure that this issue is not being caused by any unintentional changes. Thanks.

Re: Problems loading google (DNS issues possibly?)

Tue, 30 Oct 2007 12:01:19 EDT

anon posted : I live in a small town, South of Lansing, Michigan, and this exact issue was happening to me about a week ago. I lost connection to certain Google sites for 3 hours or so. I started investigating it, because I could access it from other locations. Here's what I found:

* Other folks with Comcast in Lansing proper were not having this issue.
* WireShark captures (which I saved) show what appear to be TCP RST packets being injected
* Whatever was doing this seemed to be looking for a HTTP header, specifically: "Host: google.com" or some variant - I could connect by IP - in fact I just used the IP I got from pinging google.com which worked.

IMHO, it appears as if Comcast is filtering HTTP traffic specifically - and looking for google.com in the host header. I'm not sure if someone if maliciously screwing with their bittorrent filtering software (which officially doesn't exist) or if Comcast is doing limited testing of web filtering technology, but I can say that the issue I experience was NOT a DNS issue. If anyone would like to see my packet captures, let me know.

Re: Problems loading google (DNS issues possibly?)

Tue, 30 Oct 2007 01:04:22 EDT

svideo posted : I'm seeing the same thing on Comcast in Grand Rapids, MI. DNS does not appear to be the problem. I have packet captures and a detailed description posted up here. The short version is that I'll see TCP RSTs against google but nowhere else, across 2 different IPs (my TTL had expired while testing). All other traffic works as expected, including pings to the google hosts.

Re: Problems loading google (DNS issues possibly?)

Mon, 29 Oct 2007 20:43:31 EDT

anon posted : I'm sure it isn't a DNS issue. Google's web servers respond to straight IP requests. For instance, right now www.google.com resolves as 72.14.253.103 for me (its different depending on your geographical location). If you go to »72.14.253.103/ you'll see the google start page. When Comcast is blocking Google, I get HTTP reset errors from that site, but when I goto another location (SSH Proxy tunnel through a server thats connected through Global Crossing) I can bring up that IP's website fine.

I totally agree its something with Comcast's packet filter. Whether it is intentional or not, it shouldn't be happening, and Comcast should be a LOT faster about fixing this kind of problem.

Re: Google & Hamachi VPN timeouts

Mon, 29 Oct 2007 20:21:29 EDT

scottwed posted : Thanks Atreznik, it's good to know that my symptoms are reproducible at other locations. From my location, the routes to Google and Hamachi servers are drastically different once they leave Comcast (Level3 vs ATT). I did not see the issue at all this Sunday.

So I had another thought today, this one doesn't depend upon any paranoia about private company battles. What if the packet shaper simply has a total daily traffic limit per domain? Everyone gets home from work, and starts surfing, the limit gets hit on many, but not all nights.

I'm still trying to identify when the problem starts each night, so if there is a consistent start period, then I'm going right back to 100% paranoia :)

One partial argument against the sloppy Sandvine configuration theory; I've noticed that Yahoo is still available throughout the downtime. It also doesn't explain why Hamachi is affected.

If you want full-blown paranoia, one side or the other is trying to force the issue of a "net-neutrality" bill, something that I think is well intentioned but dangerous for the Internet.

Google & Hamachi VPN timeouts

Mon, 29 Oct 2007 19:16:46 EDT

atreznik posted : Comcastic HSI in detroit area. scottwed, I'm sitting in the hotel in miami and I wanted to reply so you knew you weren't the only one. Last thursday night (10/25) was when I first noticed issues with the google domain and also VPN connections via hamachi. Fairly similar symptoms; I had it up already (hamachi) and it seemed to work fine, however when Google stopped working I tried restarting my machine and then Hamachi couldn't resolve its servers and the game was over (literally).

I didn't check for reset packets but that theory seems to make sense. I had to go out of town abruptly for work to trinidad and puerto rico and didn't get a chance to flushdns after I changed DNS servers for my router. By the way I agree with you, I have several computers behind a Dlink 1310 with TKIP and wired or wireless, it makes no difference, encryption or otherwise, not that it should. Will try a proxy when I get back as well. BTW, I like your theory about a battle between Comcast/ATT and Google.

I am interested to see someone get to the bottom of this...

Apologies for the incoherent style I'm near exhaustion. Trust me though I'm usually right on the ball.

I'm anxious to get home and see everything working okay and get Hamachi back up. That would be just Comcastic.

Re: Problems loading google (DNS issues possibly?)

Mon, 29 Oct 2007 15:42:31 EDT

telcolackey5 posted :

said by Comspastic:

I happen to know a couple of IT guy's for google here in Seattle, apparently the issue is caching servers for dns not getting updates on comcasts end.

Posts are saying that the problem is more than Comcast's caching servers, so what is Google doing differently that is causing this?

Re: Problems loading google (DNS issues possibly?)

Mon, 29 Oct 2007 15:21:53 EDT

Comspastic posted : I happen to know a couple of IT guy's for google here in Seattle, apparently the issue is caching servers for dns not getting updates on comcasts end.

Re: Problems loading google (DNS issues possibly?)

Mon, 29 Oct 2007 12:06:52 EDT

anon posted : I've been having the same problem the past few months. I talked with Tier 1 support at Comcast last night for about an hour. We reset my modem 4 times, my router, even plugged in my laptop directly to the modem. (It was more to humor the tech lady than any hope of that actually fixing it.) I've got a network engineer calling me back within a day or so. I spoke with my friends that have comcast and they all experience the exact same issue.

I wonder if their packet filter is seeing all the customer requests to google as a DDoS and blocking it for a few hours (like 4). It could be possible.

The great thing is that I can ping google.com, connect to it from my servers (who are on Global Crossing), but all HTTP traffic gets very swiftly reset.

Re: Problems loading google (DNS issues possibly?)

Sun, 28 Oct 2007 16:43:31 EDT

scottwed posted : Did some more research. I set up a 2 minute interval with wget (A web reques tool), and turned on a packet sniffer to track all Reset packets. I started the trace at ~9:50pm local time, and the problem goes away at 12am local time.

It's very consistent, I receive a properly formed Reset packet, along with another reset packet with a static sequence number. In my case, the static sequence number is 12503. The odd reset packet is sent in reply to web requests to google.com and vpn login requests to Hamachi's login servers. The problem goes away for both sites at ~midnight.

The double reset reply has the signature of the Sandvine Packet shaping appliance, known to be used by Comcast: »torrentfreak.com/images/comcast-rst1.txt

My understanding is that some ATT HSI customers are also experiencing this issue.

For the record, there is no way that this issue is related any type of Wireless encryption protocol used by an end-user or DNS configuration problem. I can consistently reach google.com using an external proxy server, and computers on other ISPs.

I'm starting to think we are getting caught in some sort of private battle between Comcast/ATT and Google.

Re: Problems loading google (DNS issues possibly?)

Sun, 28 Oct 2007 00:35:06 EDT

scottwed posted : Having the same issue. Using UT Comcast, all other websites work fine. Have to use alternate DNS IP to reach google.com. Problem is lasting hours each night. The problem always includes multiple Reset packets (part of the TCP header).

For some bizarre reason, I noticed that when the google.com problem happens, I can't reconnect my Hamachi VPN client. If the vpn session was already up, then it continues to work. If you reset the VPN connection, it will fail as it rotates through:

bravo.hamachi.cc, charlie.hamachi.cc, delta.hamachi.cc, could be more, I'm guessing there is also an alpha.

Anyone else also having the Hamachi problem at the same time?

Re: Problems loading google (DNS issues possibly?)

Sat, 27 Oct 2007 00:07:03 EDT

anon posted : Same issue.

Re: Problems loading google (DNS issues possibly?)

Wed, 24 Oct 2007 12:32:31 EDT

espaeth posted : Can you paste up a trace for when it's working? Does the hop count change?

Re: Problems loading google (DNS issues possibly?)

Wed, 24 Oct 2007 12:25:02 EDT

pokesph posted :

said by EG:

What issue does that trace reveal ?

The destination server was reached.

it may have been reached BUT it times out in a browser so it's for all intents and purposes dead and unreachable.

it did however fix itself within approx 30 mins.

Re: Problems loading google (DNS issues possibly?)

Wed, 24 Oct 2007 11:44:12 EDT

xfezz2 posted : Well at first I thought it was just me. I'm kind of relieved that its not. But at the same time it seems like a major issue. Hopefully it will be sorted out soon.

I'm still having issues. Mostly at night and the modem/router reset trick doesn't always work anymore.

Re: Problems loading google (DNS issues possibly?)

Wed, 24 Oct 2007 03:09:45 EDT

NormanS posted :

said by misbehave:

I am having the same problem.... :(

So are a bunch of 'at&t Yahoo! HSI' customers...

»Can't access Google domains.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

Re: Problems loading google (DNS issues possibly?)

Wed, 24 Oct 2007 01:50:58 EDT

misbehave posted : I am having the same problem.... :(

Re: Problems loading google (DNS issues possibly?)

Mon, 22 Oct 2007 21:26:52 EDT

EG posted :

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.86.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.134.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.

Re: Problems loading google (DNS issues possibly?)

Mon, 22 Oct 2007 17:51:44 EDT

pokesph posted : 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.86.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.134.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

Re: Problems loading google (DNS issues possibly?)

Mon, 22 Oct 2007 02:22:08 EDT

Comspastic posted : 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.

Re: Problems loading google (DNS issues possibly?)

Sun, 21 Oct 2007 16:56:56 EDT

sortofageek posted : 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 .

Re: Problems loading google (DNS issues possibly?)

Sat, 20 Oct 2007 20:00:53 EDT

anon posted : 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?

Re: Problems loading google (DNS issues possibly?)

Tue, 16 Oct 2007 23:58:27 EDT

u475700 posted : I encountered this problem today with another ISP besides Comcast.

Re: Problems loading google (DNS issues possibly?)

Tue, 16 Oct 2007 09:59:51 EDT

cork1958 posted : Seems to be a rash of sites having dns issues on the various forums I visit. :p

Re: Problems loading google (DNS issues possibly?)

Tue, 16 Oct 2007 09:11:52 EDT

tshirt posted : 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.

Re: Problems loading google (DNS issues possibly?)

Tue, 16 Oct 2007 08:16:33 EDT

espaeth posted : 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

Re: Problems loading google (DNS issues possibly?)

Tue, 16 Oct 2007 00:17:32 EDT

EnasYorl posted :

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. :hmm:

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

Re: Problems loading google (DNS issues possibly?)

Tue, 16 Oct 2007 00:02:39 EDT

u475700 posted : 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.

Re: Problems loading google (DNS issues possibly?)

Mon, 15 Oct 2007 23:39:15 EDT

c33v33 posted : 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.

Re: Problems loading google (DNS issues possibly?)

Mon, 15 Oct 2007 22:38:34 EDT

anon posted : Iv'e been having the same problem, but its not only affecting google, its also affecting Limewire

Re: Problems loading google (DNS issues possibly?)

Mon, 15 Oct 2007 20:26:35 EDT

PaisanDom posted : 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.

Re: Problems loading google (DNS issues possibly?)

Sun, 14 Oct 2007 09:21:49 EDT

andyross posted : 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.

Re: Problems loading google (DNS issues possibly?)

Sun, 14 Oct 2007 06:21:33 EDT

NormanS posted :

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

Re: Problems loading google (DNS issues possibly?)

Sun, 14 Oct 2007 03:18:23 EDT

jaminus posted : I've had the same problem from time to time over the past few weeks. I think its just Comcast being Comcastic.

Re: Problems loading google (DNS issues possibly?)

Sun, 14 Oct 2007 01:59:10 EDT

anon posted : 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.