08-21-2016 09:42 PM
Ok, now it's my turn to seek out help with a perplexing OpenDNS issue. I'm assuming rotblitz will be the one to answer since he's much more conversant with nslookup than I am.
I've been running an IPv6 tunnel service for the last several years, so of course I'm not getting OpenDNS filtering with that since most or all of my DNS traffic is going out via IPv6. That's not my problem, since it's a known issue.
Recently I changed my ISP to the local municipal ISP to get their fiber service (100 Mbps up and down, recently upgraded to 300 Mbps up and down). It works great, but I immediately had connection problems that I eventually tracked down to the IPv6 tunnel so I disabled that. I decided that I'd spend some time working with OpenDNS at my home/office, instead of only for clients and family that I support. To my surprise it doesn't appear that OpenDNS is working for me though the only thing I changed was the ISP.
For reference my router here is an ASUS RT-N66U running the latest Tomato firmware. It's had several incremental upgrades during this process. It sits behind the ISP's fiber "modem"/router (that also had one ISP initiated firmware update, but I don't know how significant it was). The DNS settings on my router point to 208.67.222.222, 208.67.220.220 and 208.67.222.220. The router is updating my IP address with DNS-O-Matic, which is updating OpenDNS and some unrelated services for me. For good measure I've got the ISP's router pointing to 208.67.222.222 and 208.67.220.220. My IP address is correctly registed for my network.
DHCP is giving the router's address for DNS server, and of course the router is supposed to be pointing to OpenDNS.
Everything looks correct and just like I always set up OPenDNS for others. However nothing is getting saved to this network's stats, and so far as I can tell, nothing is being blocked, even the domains I've blacklisted.
Here are the results for the "standard" questions we ask around here.
When I visit http://welcome.opendns.com/ I get the standard "Welcome to OpenDNS! Your Internet is safer, faster, and smarter because you're using OpenDNS. Thank You!"
C:\Windows\system32>nslookup -type=txt debug.opendns.com.
Server: RT-N66U-WiFi.HQ.BrightstarConsulting.com
Address: 192.168.15.1
Non-authoritative answer:
debug.opendns.com text =
"server 11.sea"
debug.opendns.com text =
"flags 20 0 70 5950800000000000000"
debug.opendns.com text =
"originid 0"
debug.opendns.com text =
"actype 0"
debug.opendns.com text =
"source 173.241.168.102:51003"
C:\Windows\system32>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Win7-64bit-Opti
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : HQ.BrightstarConsulting.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : HQ.BrightstarConsulting.com
Description . . . . . . . . . . . : Intel(R) 82566DM-2 Gigabit Network Connection
Physical Address. . . . . . . . . : 00-1E-4F-BB-F7-43
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8453:44ee:f968:ea0c%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.15.64(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, August 18, 2016 3:14:06 PM
Lease Expires . . . . . . . . . . : Monday, August 22, 2016 8:36:54 PM
Default Gateway . . . . . . . . . : 192.168.15.1
DHCP Server . . . . . . . . . . . : 192.168.15.1
DHCPv6 IAID . . . . . . . . . . . : 234888783
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-EC-1A-71-00-1E-4F-BB-F7-43
DNS Servers . . . . . . . . . . . : 192.168.15.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Just to be thorough I pointed the workstation I'm working with directly at OpenDNS instead of my router and reran the tests with the same basic results. Here are the results of those diagnostic commands but I don't see an differences that would account point to an issue with the router.
C:\Windows\system32>nslookup -type=txt debug.opendns.com.
Server: resolver1.opendns.com
Address: 208.67.222.222
Non-authoritative answer:
debug.opendns.com text =
"server 7.sea"
debug.opendns.com text =
"flags 20 0 70 5950800000000000000"
debug.opendns.com text =
"originid 0"
debug.opendns.com text =
"actype 0"
debug.opendns.com text =
"source 173.241.168.102:27652"
C:\Windows\system32>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Win7-64bit-Opti
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : HQ.BrightstarConsulting.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : HQ.BrightstarConsulting.com
Description . . . . . . . . . . . : Intel(R) 82566DM-2 Gigabit Network Connection
Physical Address. . . . . . . . . : 00-1E-4F-BB-F7-43
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8453:44ee:f968:ea0c%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.15.64(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, August 18, 2016 3:14:06 PM
Lease Expires . . . . . . . . . . : Monday, August 22, 2016 9:15:40 PM
Default Gateway . . . . . . . . . : 192.168.15.1
DHCP Server . . . . . . . . . . . : 192.168.15.1
DHCPv6 IAID . . . . . . . . . . . : 234888783
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-EC-1A-71-00-1E-4F-BB-F7-43
DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220
NetBIOS over Tcpip. . . . . . . . : Enabled
Any ideas of where to look or what to try?
08-22-2016 05:10 AM
"My IP address is correctly registed for my network."
This is not correct. It looks as if your IP address 173.241.168.102 is not registered for the network at https://dashboard.opendns.com/settings/ as can be seen from "originid 0". If you see it registered nevertheless, then you must raise a support ticket, because staff must check your account.
If a wrong IP address is registered, then you must check your update process from Tomato through DNS-O-Matic to get it fixed, because then your update process is broken in some way.
08-22-2016 01:42 PM
Oh, that address is definitely displayed on the dashboard. That was one of the first things I checked, along with the entire update chain through Tomato, DNS-O-Matic, and the dashboard. There might be some sort of long standing issue that I hadn't noticed because I'd been running with IPv6 for so long.
I installed the Updater to see if there might have been one of those "address mismatches" that get's asked about here from time to time, and everything is good there as well.
Opening a ticket now.
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