It's official, hell has frozen over...

I have never seen this and I never thought I would... I fire up IE, and I head over to google, I get a yahoo page with search results for google.com. ****in IE, I must have entered the URL in the yahoo search bar it installed without my permission, I don't even check to see if this is the case, now I remember why I installed mozilla.. I fire up mozilla. I head over to google... request timed out. OK I get it.. my internet connection is messed up. I ping google, yup timed out.. I check my cable modem, it's connected, I check my router its connected, I ping my router, I ping my external router port, both fine, I do a tracert to google, all addresses but google respond.. what????!!! this does not compute.... for the first time in as long as I remember I try a site BESIDES google... it comes up... alright, now I'm REALLY confused, I try google again, it times out.. ok my internet service is failing and reconnecting really quickly (that really was my first thought, I'm serious, after this long I still hadn't even considered the possibility that google might actually be down, I'm still having a hard time believing it myself.) but its true, check out this screenshot... and I cannot stress this enough people... THIS IS NOT A FAKE!!!

You should check your hosts file and make sure there's no entry for google in it.

Well you suck then since I have no issue getting to both the one you list and Google.ca (the one I usually use). :D Could be localized to your area. Did you check Internet Traffic Report to see if something is down or that perhaps you might have a spyware or something else interfering?

Quote:

---

I get a yahoo page with search results for google.com.

---

good one, I hadn't done that, but there is not an entry for google are you able to get to it?

Seems to be working just fine for me :).

I've tried in two different browsers and I'm unable to ping so I doubt its spyware, besides, its resolving the IP so I doubt its a dns issue, ping google and gimme the IP it gives you, I'll go directly to that

Quote:

---

but there is not an entry for google are you able to get to it?

---

No specific entry. What you'd be looking for is a router that might be interferring (elimination/troubleshooting to figure out what the problem is). The hosts file and/or other checks for spyware/viruses might also be necessary.

only one entry in my hosts file:
127.0.0.1 localhost

tried google.ca too and no go

Reboot?? (all purpose solution to everything... :D)

Do you have another machine on the network to try this with (visit google)?

Visit Anonymizer and see if you can get to Google through their freebie page.

www.google.com = 216.239.57.147

www.google.ca = 216.239.63.104

Maybe DNS servers in for his ISP are affected?

I know that several large sites were suffering a DNS cache poison attack several days ago?
Maybe the attackers are refining their attack?

Weird that it is redirecting to yahoo... before the attackers were redirecting to

EDIT: Don't go to these domains!
www.7sir7.com
123xxl.com
abx4.com
/EDIT: Don't go to these domains!

They were redirecting to install spyware on your PC.

Maybe I just don't see it because my DNS for those domains redirects to 0.0.0.0
They say those domains are/were using dynamic DNS...

There is an update on the DNS cache poison attacks at incidents.org

http://isc.sans.org//index.php

If you're looking at this other than today, You'll want to look at the

Handler's Diary March 13th 2005

dns issue... I'm getting IP 64.233.161.104, no response, the ip duck gave me brought up GOOGLE, PRECIOUS GOOGLE, I'll never take you for granted again!!! weird, must be a local dns server with a bad entry for google

The Duck,

When I do it I get this:

Quote:

---

C:\Documents and Settings\MsM>ping www.google.com

Pinging www.google.akadns.net [64.233.187.99] with 32 bytes of data:

Reply from 64.233.187.99: bytes=32 time=2510ms TTL=240
Reply from 64.233.187.99: bytes=32 time=73ms TTL=240
Reply from 64.233.187.99: bytes=32 time=86ms TTL=240
Reply from 64.233.187.99: bytes=32 time=89ms TTL=240

Ping statistics for 64.233.187.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 2510ms, Average = 689ms

---

it only sent me to yahoo on IE, so its probably the default search page for IE, I don't know, I rarely use it

Google has multiple IP's, maybe you got a different one because your located in canada??

Quote:

---

Pinging www.google.akadns.net [216.239.57.147] with 32 bytes of data:

Reply from 216.239.57.147: bytes=32 time=75ms TTL=241
Reply from 216.239.57.147: bytes=32 time=62ms TTL=241
Reply from 216.239.57.147: bytes=32 time=63ms TTL=241
Reply from 216.239.57.147: bytes=32 time=61ms TTL=241

Ping statistics for 216.239.57.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 75ms, Average = 65ms

---

I get the 64.233.161.104 address when I ping.

Could just be different because of clustering. They are just spreding the load across several servers. Its not uncommon for people to get different servers. Especially when several countries are involved.

That's what I meant phish, I just suck at wording things :D...

I'm not in canada, and phishphreek80 is getting the same IP I am and I assume he's able to reach google... this is weirdness. but I have your google IPs, if it goes on for too long I'll add them to my hosts file for convenience purposes

try using explorer too, not IE but explorer, open up a folder and type in www.google.com, see if that works, I know since it is giving you an ip via dns resolution you may think its fine but is it possible it cached the ip? try http://64.233.167.147 see if that works?

i may consider flushing your dns also....
open a cmd prompt and type in
ipconfig /flushdns
then
ipconfig /registerdns

see if that fixes it, if not I think msm has the next best solution

ok, now I'm getting this IP:

Quote:

---

Pinging google.com [216.239.39.99] with 32 bytes of data:

Reply from 216.239.39.99: bytes=32 time=48ms TTL=241
Reply from 216.239.39.99: bytes=32 time=34ms TTL=241
Reply from 216.239.39.99: bytes=32 time=53ms TTL=241
Reply from 216.239.39.99: bytes=32 time=33ms TTL=241

Ping statistics for 216.239.39.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 53ms, Average = 42ms

---

This proves our theory, it looks as though the server you go to depends on the amount of people using google at a given time...

Are you running your own DNS server(s)? If so, manually add googles IP to your DNS lookup table.
You can always remove it later on.

(Or, if you are just using your ISPs DNS server(s) then put it in your hosts file. Its just easier to modify a couple of DNS servers rather than updating all your workstations hosts files)

While you are at it...
redirect those 3 domains I put in my post at the top of the last page to either 0.0.0.0 or 127.0.0.1

OK gmail's gone too... this sucks. Its returning ip 64.233.179.106 no response to ping.. both worked fine less than an hour ago.

I resolve 64.233.161.105 for gmail.google.com

are you sure phish? I resolved another ip but if you go to it eg http://64.233.161.105 then you get the english version of google and not gmail

edit: fyi mine was http://216.239.57.107/

Quote:

---

C:\Documents and Settings\MsM>ping gmail.google.com

Pinging gmail.google.akadns.net [64.233.171.107] with 32 bytes of data:

Reply from 64.233.171.107: bytes=32 time=1151ms TTL=239
Reply from 64.233.171.107: bytes=32 time=63ms TTL=239
Reply from 64.233.171.107: bytes=32 time=92ms TTL=239
Reply from 64.233.171.107: bytes=32 time=87ms TTL=239

Ping statistics for 64.233.171.107:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 1151ms, Average = 348ms

---

Try the Ip and then gmail after it... eg. 64.233.171.107/gmail

Sorry, I forgot to put /gmail after the IP.

64.233.161.105/gmail

acidreign: Who's DNS servers are you using? What is your ISPs name and what nameservers IPs are you using?

If you're using Verizon, check out 151.197.0.38 and 151.197.0.39
If you're on Comcast, check out 68.82.0.5 and 68.82.0.6

I know they're not having any problems as of now. I just tested them out.

I run my own DNS server but forward to 151.197.0.38 and 39.

Also, try a public DNS server such as the ones from OpenNIC.

You'll have to use a Tier2 address...
http://www.opennic.unrated.net/public_servers.html

63.226.12.96 seems to work pretty well.

Google works for me:

Quote:

---

microburn@unerror:~> ping www.google.com
PING www.google.akadns.net (64.233.187.104) 56(84) bytes of data.
64 bytes from 64.233.187.104: icmp_seq=1 ttl=232 time=115 ms
64 bytes from 64.233.187.104: icmp_seq=2 ttl=232 time=114 ms
64 bytes from 64.233.187.104: icmp_seq=3 ttl=232 time=96.8 ms
64 bytes from 64.233.187.104: icmp_seq=4 ttl=232 time=96.6 ms

--- www.google.akadns.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 96.630/105.834/115.876/9.142 ms
microburn@unerror:~> ping google.ca
PING google.ca (216.239.59.104) 56(84) bytes of data.
64 bytes from 216.239.59.104: icmp_seq=1 ttl=226 time=211 ms
64 bytes from 216.239.59.104: icmp_seq=2 ttl=226 time=196 ms
64 bytes from 216.239.59.104: icmp_seq=3 ttl=226 time=171 ms
64 bytes from 216.239.59.104: icmp_seq=4 ttl=226 time=175 ms
64 bytes from 216.239.59.104: icmp_seq=5 ttl=226 time=172 ms
64 bytes from 216.239.59.104: icmp_seq=6 ttl=226 time=173 ms

--- google.ca ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5004ms
rtt min/avg/max/mdev = 171.050/183.472/211.517/15.179 ms
microburn@unerror:~>

---

As someone mentioned above, Google has different IPs. Those are the two I get for Google.ca and Google.com. The IP you had didn't load for me either, maybe your best bet would be to add one of the working IPs to your host file for Google for the time being, until the DNS propagates and you get a new IP for Google. Good luck, it must be tough without Google... I feel for you... /me hugs x acidreign x

microburn

*EDIT*
Didn't see phishphreek80 and the other's latests posts, someone called asking for help with their computer.


*EDIT2*
64.233.161.105/gmail wouldn't work. Well... it would, but when I go there, it forwards me to http://gmail.google.com/gmail ?

ok, now I feel really stupid, I don't know why it ONLY affected google based sites and ALL of them, but a tech support guy in tier 2 (same position I hold at my company) had me bypass my router and the same IPs gave a response. so I reset my router and all is good in google land again. sorry guys. I'm a dumbass.

Neavor mind.

I had this problem a long time ago. Im not exactly sure how i got rid of it, but its was some sort of browser hijacker? I think i ran Hijack this, and it worked just fine.

Greetz 'Cid -

Somewhere between you and Google/Gmail is an internic router I bet... one that likes crapping out at random intervals. Hang tough for now, wait another hour, see if it fixes itself - or try playing round with tracert and see how far you can get before it dies.