But also do not foget that recently there has been this problem out there for everyone. :(
Akamai DDoS Attack Whacks Web Traffic, Sites
http://forum.gladiator-antivirus.com/index...showtopic=15739Keynote was able to determine that the problems were limited to several large sites, including MSN.com, Microsoft.com and
Yahoo.com, that outsource DNS services to Akamai. Those sites were all but inaccessible until the service was restored around 10:45 a.m., Taylor said.
*********************
Now all that stuff is suppose to be in the past..but it could be happening again.
Guess i trying to tell you taht if this is just a recent problem for you it might go away all by itself if they are being ddosed again...
But also if you have WinXP for an OS..there could be a reason your problem could even last longer that usual because of this action by WinXP..
***************************
How to turn off unsuccessful ("negative") DNS caching.
(Applies only to Windows XP and Windows 2000.)
From:
http://cable-dsl.home.att.net/#dns_cache"By default the DNS Client also caches negative responses (including the lack of any response from the DNS server). Unfortunately, that can prevent you from recovering from transient DNS errors for an extended period of time. If, for example, the DNS servers at your ISP are temporarily overloaded, or slow to respond due to network congestion, the DNS Client will cache the negative response. Until that cache entry expires, which can take several minutes, it won't even try to lookup that name again -- you'll just get an immediate error. That prevents you from quickly recovering from DNS errors by simply retrying, the recommended thing to do. This can lead to frustrating delays and seeming loss of connectivity problems."See the above link to disable negative caching.
http://www.techtv.com/screensavers/answers...3384507,00.htmlIn addition when you can't get to a webpage because Windows XP or Windows 2000 has cached an unsuccessful DNS lookup, you can:
Try later (after the cache entry has expired)
Reboot your computer (which clears the DNS cache)
Clear (flush) the DNS cache manually (run "ipconfig /flushdns")
Turn off the "DNS Client" service entirely (hurts performance by requiring unnecessary lookups)