Dave’s Blog

I'm having the same problem, I have linksys, this is the first time this happened to me though.

I have this problem as well, and that's how I've been having to deal with it. Very strange DNS problem.

Just to see if there is a pattern here, I'm On a Linksys WRT160Nv3 on Comcast

Just had the same problem, and I'm also using Linksys WRT160Nv3 (I'm in Mexico, so the ISP wouldn't be to blame, I guess)

BTW, for those in OS X, to flush your DNS cache:
dscacheutil -flushcache

In the Terminal.

Thanks mate. I was seeing this issue too and it's been driving me nuts. Flushing the DNS cache fixed it.

I am having the same issue and also using the Linksys wrt160Nv3. Is there a new firmware? I have set my DNS to use the openDNS servers for DNS 1 and DNS 2 and left DNS3 and WINS empty. I notice on the status page for the router that DNS3 had the DNS from my ISP. If anyone gets this fixed I'd love to hear the solution!

same prob here, also with a Linksys WRT160N on Cox cable.

The ipconfig /flushdns (and similar commands on other OS) are, at best, a temporary solution. Over the last few months I've had this reoccur sufficiently frequently that it's aggravated both my wife and myself. Linksys WRT310N v2 here with stock v2 firmware.

What I'm trying now is overriding the DHCP assigned DNS servers with my ISP ones, rather than having the machines relay DNS requests through the router. Something is causing the DNS cache on the router itself to become poisoned somehow.

Location: Northern Alabama, AT&T DSL.

If it persists, I'll try going to DD-WRT firmware next.

Same issue, and I am using a Linksys WRT160Nv3

You guys try putting your isp's dns IP(s) on the basic config page? Seems to have done the trick over here.. Cheers :)

This is a common occurence on WRT610N and complaints have been flooding the forums. http://goo.gl/AA5m I have the WRT610N v3 and it's also happening to me. Linksys has been ignoring the complaints and is not doing anything to release a fix!

I ended up returning the WRT310N - the problem hasn't been back. It was some problem with the firmware, and Cisco's reluctance to fix the issue (or even respond to it) lead me to return it. I ended up buying a Netgear!

Thanks for the input everyone!

Funny. Kim mentioned this issue and I know she purchased a Linksys router. What about using OpenDNS with the router as fix. I use it (Belkin router) and it works just fine.

Hmmm I can't talk in that fancy language that others have - I am on a Linksys & Comcast - very frustrating !!!! I did all sorts of scans - flipped browsers. THANKS for bringing the issue to attention (and thanks @JohnLauber for sending me here to read your post :) !!!

Maybe now John will know how to help me fix it - hahaaaa

yup this happened to me yesterday where facebook redirected me to myspace. i did a screen recording to show exactly what was happening: http://www.youtube.com/watch?v=wMZPJ0n4HK8 - also, sometimes twitter redirects me to blogspot. i'm on a mac, snow leopard 10.6.3. used safari, chrome, and firefox - all gave me same problem even after clearing cache

Yes, it's your Linksys/Cisco router and here's how to fix it...

1) Do an ipconfig and you'll see that your first DNS server is 192.168.1.1
2) write down the last two DNS server IP addresses
3) go to your network adapter settings and change the TCP/IP DNS properties from automatic to manual and add your two IP addresses
4) verify the changes by typing ipconfig /all
(confirm that 192.168.1.1 is no longer in the list)
5) make this change on every computer on your network

I was having the same problem and it isn't a virus and it isn't your Linksys router. It's the internet, as these tracert command results clearly show. At times, attempts to go to Facebook's servers never even get to their servers.

C:\Documents and Settings\Sasquatch>tracert www.facebook.com

Tracing route to www.facebook.com [216.178.39.11]
over a maximum of 30 hops:

1 * <1><1>
2 7 ms 9 ms 16 ms cpe-24-94-20-1.san.res.rr.com [XX.XX.XX.XX]
3 8 ms 9 ms 7 ms wcsdca1-gsr1-ge2-1-6.san.rr.com [24.25.193.97]
4 9 ms 7 ms 8 ms gig5-0-0.wcsdca1-gsr3.san.rr.com [24.25.192.14]
5 8 ms 8 ms 10 ms so-0-0-0.gar1.SanDiego1.Level3.net [209.0.8.1]
6 9 ms 10 ms 9 ms ae-14-14.car1.SanDiego1.Level3.net [4.69.142.74]
7 15 ms 17 ms 17 ms ae-5-5.ebr1.LosAngeles1.Level3.net [4.69.133.206]
8 11 ms 12 ms 12 ms ae-4-90.edge1.LosAngeles9.Level3.net [4.69.144.202]
9 11 ms 12 ms 11 ms ve201.lax.myspace.com [4.71.32.22]
10 191 ms * 14 ms vl341.cs1.lax1.myspace.com [204.16.35.133]
11 13 ms 11 ms 13 ms vl3551.cs1.els2.myspace.com [216.178.35.73]
12 13 ms 13 ms 13 ms 216.178.39.11

Trace complete.

I am having the same issue as well. It started happening after installing the latest firmware on a Linksys WRT160N

Call Linksys technical support. They'll walk you through it. 1-800-326-7114 1 for English

I've been having this issue as well. I also have a Linksys router-- perhaps we should file a formal complaint to Linksys?

Having the same problem here, at first I though I was crazy or I was experiencing my first OSX virus. This really sucks,...

WRT160N, same problem. Configured dns manually on my adapter to use isp's dns and not the router ip. Seemed to do the trick, weird problem though...

wrt320n, same issue
must not use router dns server, but configure so that only isp dns servers are used.
always liked linksys products, now this was my last if they don't fix it.

Thanks mate. I was seeing this issue too and it's been driving me nuts. Flushing the DNS cache fixed it.

I'm having the same issue but don't have a Linksys rounter, we have a Dell. It only happens on my computer. I get the "Ooops this link appears to be broken" page, but recently my Facebook bookmark opens Twitter. This occurs on Firefox and IE but other computers on same network do no do this.

Virus trojans, spyware all scanned removed up to date and nothing detected.

Link to how to flush your DNS cache in XP and a registry entry to create to prevent this from happening: http://www.tech-recipes.com/rx/233/clear_windows_dns_cache/

hell0....

It's so bloody annoying that Cisco will not fix this and choose to ignore and deny the problem. Big corporates just don't care!

I've found my own solution, but I'm using dnsmasq on a ubuntu server and using the specific nameservers in the dnsmasq.conf (server=<isp>t have to change the network properties on every every machine connected to my network. May help someone with a similar set up.