OpenDNS Forums
The official support and discussion site of OpenDNS
Support
K-12 Forums
Categories
- Administrative
- Adult site blocking
- DNS-O-Matic / dynamic IPs
- Domain blocking
- Domain Name System (DNS) troubles
- Mobile instructions
- OpenDNS services
- Proxies, accelerators, and more
- Router instructions
- Satellite
- Shortcuts
- Wishlists and feature requests
-
Feeds
Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.
-
Well, here is the issue, DNS servers for COX San Diego have been down for 2 days with no ETR. I set up my CISCO WRT400N router following the instructions with he 2 new DNS addresses. Then I get the error ( I am saving and even rebooting the router)
A few minutes later the updater shows that I am on OpenDNS, but it only lasts for 3 - 5 minutes. Which it reverts back to not using OpenDNS. I open my router config and it still shows the DNS addresses. The application I am using OpenDNS for is World of Warcraft if that helps. -
- CommentAuthormaintenance
- CommentTimeNov 4th 2009
As far as WoW goes, once you are connected to a game server, DNS is out of the picture, so if you can get IP addresses of the servers and use those to connect, you can bypass the DNS problem for now.
As to the "Oops", can you browse the web normally? You must be getting name resolution somewhere, since you can get to the OpenDNS Welcome page. Do you have any "connection assistant"-type software from Cox installed? Any other internet software? These may give you a false negative, or override your DNS settings. I assume the router is behind the cable modem - would the Cox modem override the router settings?
Does the router have spaces for more than two DNS server settings? Fill them.
http://www.opendns.com/support/article/197
Check also in the computer network settings (if you need help, follow the instructions for setting OpenDNS up on your computer). Make sure the computer DNS settings point only to the router, and not to any other DNS server.
You may also wish to empty your browser cache, and clear the local resolver cache. The latter can be accomplished via a reboot or the
ipconfig /flushdns
command entered at the command line (for Windows).
Otherwise, you may post the output of
ipconfig /all
here for analysis.
Also, do this: http://www.opendns.com/support/article/129
1 to 2 of 2
