Can't Get OpenDNS To Work - IP Mismatch Issue

bababooyah · ‎12-09-2013

FYI, I have submitted a trouble ticket with OpenDNS for this issue as well.

Background --

System - HP Pavillion desktop running Windows 7 Professional Service Pack 1

Processor - Pentium Dual Core E6300 @ 2.8 GHz RAM - 3GB

Network details - various wired and wireless devices connect first to a Linksys (Cisco) E2000 router, then on to a CenturyLink 660 Series DSL modem.

I have followed various FAQs and Forum threads in an attempt to troubleshoot my issue which continues to be an IP mismatch. Specifically, when running the OpenDNS Updater utility, I get the following message:

"Your OpenDNS filtering settings might not work due to DNS IP Address (xx.xx.xxx.xxx) and HTTP IP address (something other than xx.xx.xxx.xxx) mismatch".

CenturyLink is a very difficult company to deal with and I am confident that if I have to actually have a dialogue with them about resolving these issues, they will be clueless and I will never get OpenDNS to work.

Here is what I have tried so far:

1.) The step by step process as outlined in the following (I had to go by several similar Linksys routers to take an educated guess at mine but the answers seem to be pretty consistent): https://store.opendns.com/setup/device/linksys_e1500

2.) Followed the advice that pertained to Linksys routers in this Forum thread: https://support.opendns.com/entries/21882330-OpenDNS-not-working

3.) Cleared the DNS cache: http://www.opendns.com/support/article/68

4.) Cleared my Firefox browser cache: https://support.mozilla.org/en-US/kb/how-clear-firefox-cache

5.) Went back and input DNS3 info per Forum thread: https://support.opendns.com/entries/21882330-OpenDNS-not-working

6.) Changed DNS1 and DNS2 servers to match information contained on your main OpenDNS Store Web page: 208.67.222.222, 208.67.220.220

7.) So right now the DNS table in the Setup utility for my router looks like this:

DNS1 - 208.67.222.222

DNS2 - 208.67.220.220

DNS3 - 208.67.222.220

And it's just not working. Nothing is happening. Thankfully everything else but OpenDNS is still working, but that's not making me happy. I want to get this up and running, without having a dialogue with CenturyLink about an IP mismatch. Please tell me that there is another way, thanks.

rotblitz · ‎12-09-2013

It seems your ISP put you behind a proxy. What does http://welcome.opendns.com/ say?

See also https://support.opendns.com/entries/23644725-Can-t-get-OpenDNS-to-work-

rotblitz · ‎12-09-2013

"IP Mismatch Issue"

Your HTTP IP address: http://myip.dnsomatic.com/
Your DNS IP address : nslookup myip.opendns.com.

bababooyah · ‎12-09-2013

It seems your ISP put you behind a proxy. What does http://welcome.opendns.com/ say?

It says "Oops, you don't seem to be on OpenDNS, let's see if we can fix that".

"IP Mismatch Issue"

The two addresses do not match.

bababooyah · ‎12-09-2013

Correction - when I run the DNS IP address command on my main computer which is wired to my network, I get a different IP address than my HTTP IP address.

When I run the DNS IP address command on a computer that is connected via wireless, I get a timeout error, can't even get an address back.

Maybe OpenDNS is just not cut out for me, or vice versa :)

Thanks for your continued support.

rotblitz · ‎12-09-2013

"I get a timeout error, can't even get an address back."

Something is misconfigured on this computer. Start with trying:

nslookup -timeout=12 myip.opendns.com.

You may want to copy & paste the complete plain text output of this here.

bababooyah · ‎12-09-2013

Sorry, I'm not comforable pasting specific IP information about my network in an open forum. Are you an OpenDNS employee? Is there a secure email address or trouble ticket system that we can work through here?

Should I be taking these actions on the wired computer, the wireless computer, or should it even matter?

Here's what I got:

C:\Users\XXX>cd\

C:\>nslookup -timeout=12 myip.opendns.com. DNS request timed out. timeout was 12 seconds. Server: UnKnown Address: xxxx:xxxx:xx:ffxx:xxx:d::

DNS request timed out. timeout was 12 seconds. DNS request timed out. timeout was 12 seconds. *** Request to UnKnown timed-out

rotblitz · ‎12-09-2013

"Are you an OpenDNS employee?" - No, just a user like you. But what you show is already sufficient.

"Should I be taking these actions on the wired computer, the wireless computer, or should it even matter?"

On the computer where you got this timeout when executing nslookup.

"Here's what I got:"

You don't have valid DNS resolver addresses configured or obtained on this device, or you don't have internet connectivity. It even cannot show the DNS server address being used.

Also, it seems you have IPv6 connectivity enabled. You should disable this if you intend to use OpenDNS content filtering and stats and such. These features do not work with IPv6 yet, just with IPv4, because you cannot register an IPv6 address with your OpenDNS network.

bababooyah · ‎12-09-2013

I truly appreciate your input and assistance on this @rotblitz but I have reached a point where it's just getting too much and the potential downfalls of playing with settings that I am not entirely comfortable with outweigh any potential benefits that I might get from getting OpenDNS up and running. All of my systems are working perfectly right now, I am typing this from a remote wireless PC that clearly has full Internet access and I want to keep it that way. My hopes were that OpenDNS would simply be turned on and work with minimal changes in router or other settings, that is not the case. It is quite possible that I have a problem, or many problems, but they aren't apparent from my day to day network behavior, and no one has hacked in or created havoc otherwise in the 10+ years that I've been up and running here. I have many other safeguards implemented and will continue to do so, but for the foreseeable future, OpenDNS is just not going to work for me. Thanks anyway and best of luck to you.

Report Inappropriate Content · ‎12-10-2013

Hi,

It looks like you have already opened multiple support tickets regarding this issue and one of my colleagues is handling the request. In general, the mismatch maybe due to the way your ISP handles your DNS traffic and HTTP traffic. We will continue to investigate the issue in your support ticket.

rustyiron · ‎09-29-2014

Problem solved!

I just discovered that my desktop computer, which is hooked up to Time Warner Cable, was using their own DNS, despite my computer and routers being configured to use OpenDNS. Time Warner is hijacking all DNS requests and rerouting them to their own servers. A call to the customer service people was a waste of time. They're only helpful if you need to unplug your modem and plug it back in. I was on my own. The clue that led me to the solution was my iPhone, which when connected to my home network, would use OpenDNS.

The iPhone connects to my Airport Extreme router, which is connected to the Time Warner router. My desktops, although physically connected to the Airport Extreme, were using the IP number for the Time Warner router.

The solution was to configure my iMac manually, using the IP number for the Airport Extreme, rather than the IP number for the Time Warner router. BAM! Problem solved.

melaneyc · ‎02-14-2015

I am having this same problem, but I don't know how to configure my desktop manually using my router's IP instead of Time Warner's. Can anyone help me? I have a windows computer.

rotblitz · ‎02-15-2015

Here you go: https://support.opendns.com/forums/21618384-Computer-Configuration

Use your router's IP address instead of the OpenDNS resolver addresses then.

Anonymous · ‎02-17-2015

Since our resolvers will not understand your routers private IP address–you will need to input your networks public IP address. You can find your public IP address by visiting: http://www.whatismyip.com/.

rotblitz · ‎02-17-2015

Confusing... confused now...

I believe it was not about registering an IP address at https://dashboard.opendns.com/settings/ but about configuring a DNS server address on a device behind a router configured for OpenDNS use. The router's private LAN facing IP address is just right for this. Even more, entering the public IP address will definitely break DNS, because this has most likely no DNS server behind it and cannot respond to DNS lookups at all.