OpenDNS not working - I'm getting the OOPS Page
My router, which used OpenDNS, died. I replaced it with a Cradlepoint router, which I configured for OpenDNS (free version). I'm now getting the OOPS page at: http://welcome.opendns.com
To troubleshoot I have:
Flushed DNS cache
Flushed Browser cache
Confirmed - Dynamic IP Update is checked on my OoenDNS dashboard
Confirmed -PDNS and SDNS addresses: 208.67.222.222 and 208.67.220.220 respectively
The one thing I'm not sure about is my router's 'LAN Gateway Address' setting, which is listed with the primary and secondary DNS fields . I set the 'LAN Gateway Address' field to the address used to access router admin via a browser i.e., 192.168.0.1 Is this correct?
Bottom line: can you help me troubleshoot my OpenDSN disconnect and ultimately rid of the OOPS screen?
Thanks for any help.
-
" I set the 'LAN Gateway Address' field to the address used to access router admin via a browser i.e., 192.168.0.1 Is this correct?"
No idea, I had to take a look in your user manual or at least would need to see a screen shot.
Regarding your problem, execute the following command in a command prompt window:
nslookup -type=txt debug.opendns.com.
If it does not show an error, then copy & paste everything here, else if it says something about "non-existent domain debug.opendns.com", then post the complete plain text output of the following command:
nslookup -type=txt debug.opendns.com. 208.67.220.220
-
The output you requested is on the attachment. Thanks for your help.
NickVA_ Attachment.doc -
Attached are my Cradlepoint router admin pages showing 'LAN Gateway Address' field and other addresses. Thanks.
NickVA_ RouterSettings.doc -
With your current router configuration your DNS queries do not go to OpenDNS, but you could use OpenDNS. Did you execute the commands with the same configuration as shown in your router screen shot? If so, this configuration does not do what you expect it to do.
If you read your manual (http://cradlepoint.com/sites/default/files/productdocs/MBR95_Manual_3.6.3.pdf), you better go into Network Settings > DNS and enter the OpenDNS resolver addresses there. As you can see from page 51 on, this router has full OpenDNS integration, including DDNS updates via DNS-O-Matic.
If you detect that your router has a firmware different from indicated in the manual, you may want to flash it with the OEM firmware from Cradlepoint.
http://cradlepoint.com/firmware/MBR95
You can do this only if you have the access credentials for your internet access, and if you haven't subscribed to special services of your ISP like IPTV or VoIP with router integration, else these services may no longer work. -
Did you execute the commands with the same configuration as shown in your router screen shot? YES.
There is no "DNS' selection under "Network Settings"
I had applied the latest firmware.
Primary and Secondary DNS settings are located at: System Settings >>> Administration >>> "Router Services" page, You have a screen shot of this page.
You said, "With your current router configuration your DNS queries do not go to OpenDNS. " Can you explain why this is? I've configured the router properly as far as I know. ...
-
Ok. I went back to older firmware and I'm now getting the "Welcome to OpenDNS!" screen. Then I did the following:
- Flushed DNS cache
- Flushed Browser cache
- REMOVED - Dynamic IP Update check on my OpenDNS dashboard (grasping at straws).
- Manually ran OpensDNS Updater V2.2.1
- Confirmed - Router’s PDNS and SDNS addresses: 208.67.222.222 and 208.67.220.220 respectively
- Confirmed OpenDNS filter settings.
- Rebooted PC and router.
- Reran your earlier RUN commands (see attachment)
Fifteen minutes later, nothing is being blocked. Any suggestions?
CMD_Output2.doc -
rotblitz - I want to show you something. The attachment show (3) Cradlepoint router screenshots with each containing DNS info. The 1st screenshot shows :
"DNS Servers: 216.144.187.199, 204.186.80.251, 216.144.187.101 " . Shouldn't it be listing OpenDNS - PDNS and SDNS addresses: 208.67.222.222 and 208.67.220.220 ?The other (2) screenshots reflect the OpenDNS DNS addresses.Again, any help you can offer is much appreciated. -
rotblitz - It helps if I send the attachment.
Cradlepoint DNS Screenshots.doc -
UPDATE: rotblitz, my OpenDNS filter was "customized" blocking porno, sexuality and some other categories. Up to this point my confirmation tests included checking the "Welcome" page followed by checking different porno sites. The porno sites were not being blocked.
Again, grasping at straws, I decided to change from a "custom" filter to selecting the "Highest" filter setting. Lo and behold - porno sites are now being blocked.
The problem I now have is that there are categories in the "Highest" filter that I do not want filtered. Any suggestions.
P.S. nslookup -type=txt debug.opendns.com - no longer shows an error.
-
"You said, "With your current router configuration your DNS queries do not go to OpenDNS. " Can you explain why this is?"
Because your first nslookup against 192.168.0.1 (your router) returned "Non-existent domain". If you used OpenDNS, the request would be answered with valid TXT records, as in the second nslookup which you forced to go to OpenDNS.
"REMOVED - Dynamic IP Update check on my OpenDNS dashboard (grasping at straws)."
Then you can't update your IP address information any longer with e.g. an Updater. Bad idea!
"Reran your earlier RUN commands (see attachment)
Fifteen minutes later, nothing is being blocked. Any suggestions?"Your router is still not using OpenDNS: non-existent domain for debug.opendns.com TXT records.
""DNS Servers: 216.144.187.199, 204.186.80.251, 216.144.187.101 " . Shouldn't it be listing OpenDNS - PDNS and SDNS addresses: 208.67.222.222 and 208.67.220.220 ?"
Indeed, it should. You see, you're not using OpenDNS, but 216.144.187.199, 204.186.80.251, 216.144.187.101. Exactly as I said before.
"Again, any help you can offer is much appreciated."
Now asking me why? I would know if I would be Mr. Cradlepoint, but I'm Mr. RotBlitz. ;-)
"my OpenDNS filter was "customized""
You simply can forget your dashboard settings as long as your router doesn't send the DNS queries to OpenDNS. The settings are irrelevant then. Bad enough, it seems to inconsistently sometimes use OpenDNS and sometimes not. You'll have to find out from Cradlepoint support what you have to do to only use static DNS server addresses you want to use, not randomly these and any others, e.g. your ISP's. It may be a firmware glitch, not quickly to be fixed.
-
Rotblitz - My OpenDNS is now working as it should ?!? . I may have an answer to why. Cradlepoint integrated an OpenDNS feature into its router software. However, when you use that feature, it creates an OpenDNS "Premium" network with your OpenDNS credentials. There is no Cradlepoint option to create the OpenDNS home "free" service. Grasping at straws, I decided to create the "Premium" network on my OpenDNS account through Cradelpoint. I then deleted the 'Premium' network on my OpenDNS account, leaving only my OpenDNS home free network active. The "Premium" network remains listed on my OpenDNS account but zero networks are assigned to it. Here's what I think happened. So long as I did not create an OpenDNS "Premium" network through Cradlepoint, the Cradlepoint router was not being configured to use OpenDNS. Once I applied my existing 'free' OpenDNS credentials to create an OpenDNS "Premium" network, the Cradlepoint router was then rightly configured to use OpenDNS.
I rechecked "Enable dynamic IP update" - as you suggested.
Thank you for your time and help. Much appreciated! - Nick
-
Wow, just wow, excellent! I see you overcame all hurdles. Thanks a lot for the feed-back. It will be of much use for other users in the same situation.
Btw, the internet is full with related information: https://startpage.com/do/search?q=cradlepoint+opendns
Please sign in to leave a comment.
Comments
12 comments