cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
386
Views
1
Helpful
23
Replies

OpenDNS Updater and filtering settings.

xxhuwm
Level 1
Level 1

Hello, I have OpenDNS Updater installed on my computer and it was working properly until a few weeks ago, when my ISP changed my modem to a Motorola SBV6220 (I don't know if that's relevant but it's the only thing I can think of that might be causing this problem).

Now the Updater shows: "Your OpenDNS filtering settings might not work due to DNS IP address (2...) and HTTP IP address (1...) mismatch."

 

I would like to be able to filter website categories again. Can someone please help me?

Thank you very much.

 

P.S. If I go to http://welcome.opendns.com it says: "Welcome to OpenDNS!
Your Internet is safer, faster, and smarter
because you’re using OpenDNS.
Thank you!"

and http://www.internetbadguys.com shows: "This domain is blocked."

23 Replies 23

alexahar
Cisco Employee
Cisco Employee

I can confirm that your DNS IP is the 201 one, and the HTTP one may be a proxy on network. To test for one, use the following tests:

What do you see when you visit the following four websites:
http://myip.dnsomatic.com
https://myip.dnsomatic.com (you may need to accept the security certificate exception, but it is safe to proceed to this site)
http://www.whatismyip.com
http://www.lagado.com/proxy-test
Also, would you mind sending in a screenshot of the updater client? Instructions to take a screenshot can be found here: http://take-a-screenshot.org. You may wish to do so to support@opendns.com to post it privately (and update this to let us know you've submitted one). 

rotblitz
Level 6
Level 6

How frustrating is this?  Most tests have been performed and the results posted above already...

Summarizing:

  • He does have a DNS and web IP address mismatch: DNS IP address (201.130.***.1) and HTTP IP address (177.249.***.**1.)
  • It seems he is not behind a proxy or caching server, so the ISP or peering network carriers may just do different routing for DNS and web traffic.
  • He's located in Mexico and uses the OpenDNS Dallas DC.
  • The IP address registered with his dashboard isn't the DNS IP address.
  • He should not run an updater, because this would update the dashboard with the web IP address.
  • He must keep IPv6 connectivity disabled.

So, the anticipated solution can only be to manually update his dashboard network with the 201.130.***.1 IP address.  Fingers crossed that this DNS IP address doesn't change much often...

tedkramer
Level 1
Level 1

@Alexander Harrison

Rotblitz is right. But, here are the results, anyway:

http://myip.dnsomatic.com/: 177...63
https://myip.dnsomatic.com/: 177...63
http://www.whatismyip.com/: 177...63
(All IPs are exactly the same)
http://www.lagado.com/proxy-test: "This request appears NOT to have come via a proxy."


OK, I'll send you the screenshots. Although, here's what it says:
· IP address: 201... (I believe this address hasn't changed since I started this thread)
· Using OpenDNS: Yes
· "Your OpenDNS filtering settings might not work due to DNS IP address (201...) and HTTP IP address (177...) mismatch."

· Send Dns-O-Matic updates is unchecked.

[By the way, I was able to log in to the forum just now, using the account with which I started this thread, but, only for a few minutes. I sent you an e-mail about this the other day. The error says: "We are unable to log you into the support portal at this time. Please email support@opendns.com and we can assist with your issue.
Please mention that the error returned by the support portal was: User is invalid: Email: has already been taken."]

Anyway, I would appreciate it if you could implement rotblitz proposed solution with either account (I can't seem to find an option to that myself).

 

@rotblitz
Thank you for your post. That was very helpful.

"So, the anticipated solution can only be to manually update his dashboard network with the 201.130.***.1 IP address.  Fingers crossed that this DNS IP address doesn't change much often..."
Yes, this seems like the only solution at this point.

alexahar
Cisco Employee
Cisco Employee

The above does confirm that the mismatch isn't an issue of not being configured, but rather a DNS-HTTP IP mismatch on the network itself and you'll need to update your IP manually since there is the mismatch. 

With regards to your account, it looks like you've changed the email on your account and the forum hasn't caught up with that. What's the email you use to log into your original account (you can send to support@opendns.com and note that you did here) and we can work on getting your forum account working once again by resolving the email conflict. 

tedkramer
Level 1
Level 1

"...and you'll need to update your IP manually since there is the mismatch."

Could you, please, tell me how to do that? If I login to my dashboard it only detects the HTTP IP address and, as I said above, I can't find an option to set the DNS IP address.

 

About the e-mail: Yes, I've send a report about that and I confirmed that I had changed the e-mail address during the past few days.

Thank you.

rotblitz
Level 6
Level 6

"Could you, please, tell me how to do that? ... I can't find an option to set the DNS IP address."

There is no such option.  If you want to do it yourself, you had to delete your network at https://dashboard.opendns.com/settings/
Then you set one up from anew where you have the chance to enter any IP address manually.  Enter the IP address which is returned by the command:

   nslookup myip.opendns.com.

This is most likely this 201.130.***.1 IP address.  You may get a notification then that the IP address must be approved by staff.

tedkramer
Level 1
Level 1

Thank you rotblitz. I created a new network with that address but I couldn't verify it (received a link by e-mail). I got a message that says:

"Your IP (177...) does not match the one you are trying to verify.
If you can, please click the link from that IP address to verify it.
If you cannot, please contact us and explain your ownership/management of the IP address in question."

So, I created a request (#143290). Let's see how it goes...

alexahar
Cisco Employee
Cisco Employee

Your network should be all set (the verification issue is due to the same HTTP DNS mismatch) and I've verified your network to your account on our end. 

tedkramer
Level 1
Level 1

Thank you so much, guys. It works! :)