Well, just got in the office this morning, and I can get there fine. Go fig.
Printable View
Well, just got in the office this morning, and I can get there fine. Go fig.
Maybe a MyDoom side effect?
http://www.enterpriseitplanet.com/se...le.php/3387511
That's what I suspected. When Google was hit, someone started a thread with an almost identical question to mine. He couldn't reach Google, but everyone else at the time could. We found out later that MyDoom was using Google to search out e-mail addresses.
//edit -- Bingo.
SOURCEQuote:
Once Zindos has infected a machine it causes the machine to request the http://www.microsoft.com/ domain in an infinite loop, with 50ms delays. This behaviour could help to explain the difficulties some Reg experienced visiting the software giant's website earlier this week.
Well mydoom.b modified some hosts files, and didnt allow you to get to some sites. Its not cuz mydoom would try and dos them but because it was blocking you from goin there in the hosts file. Well i guess you can get there now but maybe you had mydoom.b and you just got rid of it? check it out.
Well, AV's updated and hasn't warned me of any MyDoom attacks...hmm...
it is possible that it could be a new variant... i know here we had more problems with the gaobot variants than we had combined blaster/sasser
taken from http://www.us-cert.gov/cas/techalerts/TA04-028A.html
Quote:
The virus overwrites the hosts file (%windir%\system32\drivers\etc\hosts on Windows NT/2000/XP, %windir%\hosts on Windows 95/98/ME) to prevent DNS resolution for a number of sites, including several antivirus vendors
127.0.0.1 localhost localhost.localdomain local lo
0.0.0.0 0.0.0.0
0.0.0.0 engine.awaps.net awaps.net www.awaps.net ad.doubleclick.net
0.0.0.0 spd.atdmt.com atdmt.com click.atdmt.com clicks.atdmt.com
0.0.0.0 media.fastclick.net fastclick.net www.fastclick.net ad.fastclick.net
0.0.0.0 ads.fastclick.net banner.fastclick.net banners.fastclick.net
0.0.0.0 www.sophos.com sophos.com ftp.sophos.com f-secure.com www.f-secure.com
0.0.0.0 ftp.f-secure.com securityresponse.symantec.com
0.0.0.0 www.symantec.com symantec.com service1.symantec.com
0.0.0.0 liveupdate.symantec.com update.symantec.com updates.symantec.com
0.0.0.0 support.microsoft.com downloads.microsoft.com
0.0.0.0 download.microsoft.com windowsupdate.microsoft.com
0.0.0.0 office.microsoft.com msdn.microsoft.com go.microsoft.com
0.0.0.0 nai.com www.nai.com vil.nai.com secure.nai.com www.networkassociates.com
0.0.0.0 networkassociates.com avp.ru www.avp.ru www.kaspersky.ru
0.0.0.0 www.viruslist.ru viruslist.ru avp.ch www.avp.ch www.avp.com
0.0.0.0 avp.com us.mcafee.com mcafee.com www.mcafee.com dispatch.mcafee.com
0.0.0.0 download.mcafee.com mast.mcafee.com www.trendmicro.com
0.0.0.0 www3.ca.com ca.com www.ca.com www.my-etrust.com
0.0.0.0 my-etrust.com ar.atwola.com phx.corporate-ir.net
0.0.0.0 www.microsoft.com.
i dont think it did it in any other variants of mydoom so i think its definitely a possibility that you coulda had that. Could of maybe been a dns issue with your ISP or one of your servers at work too?
It works fine for me.
Because having it up and running means people can:Quote:
why would you want to go to microsoft.com anyway? You'd think it would be a good thing for it to be off the web
1. Download updates for one of the most used OSes in the world
2. Seek help and support from their documentation section
3. Order the free security CD updates
4. Beta testers report bug information back to MS regarding future security patches
Having microsoft.com online and working means a lot more people can patch their OS, and that means less zombine infections. Never underestimate the power one site alone can have, regardless of who owns it.