03-11-2015 05:10 PM
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."
03-12-2015 04:28 AM
Post the complete plain text output of the following diagnostic commands here:
nslookup -type=txt debug.opendns.com.
nslookup www.exampleadultsite.com.
03-12-2015 11:09 AM
Hi, Rotblitz. Here are the results:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\User> nslookup -type=txt debug.opendns.com.
Server: resolver1.opendns.com
Address: 208.67.222.222
Non-authoritative answer:
debug.opendns.com text =
"server 9.dfw"
debug.opendns.com text =
"flags 20 0 2F4 5950800000000000000"
debug.opendns.com text =
"originid 0"
debug.opendns.com text =
"actype 0"
debug.opendns.com text =
"source 201.***.***.1:23***"
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\User> nslookup www.exampleadultsite.com.
Server: resolver1.opendns.com
Address: 208.67.222.222
Non-authoritative answer:
Name: www.exampleadultsite.com
Address: 67.215.92.210
Thank you.
03-12-2015 11:58 AM
The problem with the filtering not working is because your network at https://dashboard.opendns.com/settings/ is not updated with your IP address 201.***.***.1. Therefore OpenDNS cannot associate your DNS queries with your settings, and these cannot take effect.
"Now the Updater shows: "Your OpenDNS filtering settings might not work due to DNS IP address (2...) and HTTP IP address (1...) mismatch.""
Your DNS IP address is 201.***.***.1 (nslookup myip.opendns.com.), and your HTTP IP address is as of http://myip.dnsomatic.com/ If these are different, then your ISP does some tricky things with your internet connection, be it a proxy or NAT or caching.
In order for your filtering settings and stats to take effect, your DNS IP address must be registered with OpenDNS, not your web IP address.
And you may want to perform the following tests to see if there's something your ISP does with your connection.
http://www.lagado.com/proxy-test
http://www.lagado.com/tools/cache-test
03-12-2015 12:32 PM
Yes, the DNS IP starts with 201. and the HTTP IP starts with 177. (http://myip.dnsomatic.com/).
Then they must be doing something differently because, as I said, it had been working just fine in 2014 and early 2015 (I haven't changed ISP).
My results were:
http://www.lagado.com/proxy-test
Here are the raw details of the request received by this server.
Remote Host 177-***-**-**1-cable.cybercable.net.mx IP Address 177.***.**.**1
Request Protocol HTTP/1.1 Method GET
Request Headers
Host | www.lagado.com |
User-Agent | Mozilla/5.0 (Windows NT 6.1; rv:36.0) Gecko/20100101 Firefox/36.0 |
Accept | text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 |
Accept-Language | en-GB,en;q=0.5 |
Accept-Encoding | gzip, deflate |
DNT | 1 |
Connection | keep-alive |
This Server Host www.lagado.com IP Address 27.131.76.84
Date: Friday 13 Mar 2015 6:22:28 GMT+1100
Please Note: The conclusion that the request did not come via a proxy is based on the absense of the Via, Forwarded, X-Forwarded-For and Client-ip headers. It is still possible that a proxy is handling the request without announcing itself in the recommended way. (see rfc2616 & draft-ietf-http-v10-spec-01 & Squid Configuration Guide & Squid Release Notes 1.1)
http://www.lagado.com/tools/cache-test
· Serial number changed ("If the page serial number has changed you may not be using a caching proxy. To be more certain check the page age.")
· The page was only a few seconds old ("If the page age is no more than a few seconds there is no evidence of caching occuring so a proxy is not evident; stop here - No Proxy Found")
03-13-2015 03:33 AM
Ok, most likely no proxy and no caching, but could still be NAT.
As I said, you must register your DNS IP address at https://dashboard.opendns.com/settings/ to make filtering and stats work. And you cannot use the usual updaters to keep it updated, because these would overwrite it with your web IP address. Therefore, registering your DNS IP address with OpenDNS makes sense only if your DNS IP address doesn't change. You had to find this out by looking yourself or by asking your ISP.
Alternatively, you can call up your ISP to find out why they route your DNS traffic differently from the rest of your traffic, and if there's a possibility to opt out from this different DNS traffic routing.
03-13-2015 06:16 AM
xxhuwm, would you please run the following diagnostic tool on one of the computers on your network and copy, paste and comment the URL of the results so that we can further investigate why you are seeing the mismatch error?:
[Windows Diagnostic Tool](http://www.opendns.com/download/windows/diagnostic)
[Mac Diagnostic Tool](http://www.opendns.com/download/mac/diagnostic)
The link required after the test will look like the one found here:
https://support.opendns.com/entries/21841580
The results in the URL are only viewable to OpenDNS support staff and may reveal more information about why your DNS and HTTP IPs are different.
03-13-2015 12:56 PM
@Rotblitz Thank you for your help, my friend. I'll see if I can get any assistance from my ISP.
@Kristy Here's the result: https://diagnostic.opendns.com/d/4823553283194880
Thank you very much. :)
03-13-2015 01:10 PM
I'm not sure why this didn't come up when you initially ran the command nslookup -type=txt debug.opendns.com. for rotbliz, but I'm seeing Comcast's IPv6 DNS servers configured on your machine. Please try using the instructions here to disable IPv6: https://support.opendns.com/entries/54333874 and see if that removes the mismatch error on the updater client.
03-13-2015 01:36 PM
Oh! I'm sorry, I've tried everything I can think of these last few days, so I implemented this (didn't work): https://support.opendns.com/entries/26056194-Does-OpenDNS-support-IPv6- and I forgot to revert it.
I also tried disabling IPv6, yesterday (and a few minutes ago, after I saw your reply), and it didn't work either.
I reverted that setting to "Obtain DNS server address automatically": https://diagnostic.opendns.com/d/6004950945497088
P.S. It seems like the DNS IP address remains the same (201...), after I reset the modem. It's only the HTTP IP address that changes.
03-13-2015 01:41 PM
Would you please disable IPv6 and re-run the diagnostic tool? It may reveal what is actually happening but based on your current results that is the only issue I see.
Once IPv6 is disabled please clear your caches and run the standard test here: https://www.dnsleaktest.com/ and confirm that you only see OpenDNS resolvers. If you see a different DNS service please specify which one.
03-13-2015 01:50 PM
OK.
· IPv6 disabled: https://diagnostic.opendns.com/d/5914294386425856
· DNSleaktest: There's 5 servers (302 Direct Media LLC) and they all start with 204.194.238.
03-17-2015 02:55 PM
Hi, I'm the original poster (I get an error when I try to login to the forum). Could someone from OpenDNS please have a look at the information I provided above?
Thank you so much.
03-18-2015 12:04 PM
Based on the diagnostic test, it looks like your configuration is good; however, the IP registered to your Dashboard doesn't match your current IP. To resolve this, please confirm that your updater client in it's settings has the check box for "Send updates to DNS-O-Matic" not checked.
Note the servers 204.194.238.X are all part of our Dallas datacenter (you can see the list at https://www.opendns.com/data-center-locations/) and that confirms you are using OpenDNS on IPv4 at this time.
03-18-2015 12:51 PM
"Send updates to DNS-O-Matic" is unchecked.
OpenDNS Updater still shows: "Your OpenDNS filtering settings might not work due to DNS IP address (201.130...) and HTTP IP address (177.249...) mismatch. Learn more."
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide