DDNS Issues
I've been unable to get my router (Linksys WRT110) to take a static DNS. No matter what I enter, after a reboot the status page always shows the ISP's dynamic DNS address. From what I can gather this is a problem with this brand of router; if IP is dynamic, then so is DNS. So I thought I'd try a new router. However, before I do I want to clarify some things:
1) The OpenDNS Updater gives me a message saying my HTTP IP address and my DNS IP address is different and this is a problem. However, even if I do set a static DNS, this will still be the case as my ISP gives the router one IP address and I'll still be setting the DNS address differently.
2) The OpenDNS Updater is showing my IP address as something completely different than my router is showing (router: 173.20.168.176, Updater: 67.63.55.33) What's up with that?
Thanks for any help.
-
It doesn't seem to be a problem with your router, but with your ISP. If your DNS IP address is different from your web IP address, then you cannot use the enhanced configurable features of OpenDNS (content filtering, stats), but maybe still pure DNS and content filtering with FamilyShield only.
The mismatch between DNS and web IP address may occur if your ISP put you behind a proxy or caching service.
http://www.lagado.com/proxy-test
http://www.lagado.com/tools/cache-testYour DNS IP address: nslookup myip.opendns.com. 208.67.220.220
Your web IP address: http://myip.dnsomatic.com/There is not really a solution for using OpenDNS Home Basic with all features. You'll use OpenDNS as pure DNS service or statically preconfigured with the FamilyShield addresses. An ISP change or service change may help too.
-
It doesn't appear (according to those links) that there is a proxy. I looked up the address the OpenDNS Updater came up with (67.63.55.33) and it's some other company out in Bellvue, WA. My router doesn't list this address at all. Now, about the DNS and IP addresses being different: I thought that was the point of assigning a DNS address to look at OpenDNS? I tried using FamilyShield originally and that didn't work either.
-
"Now, about the DNS and IP addresses being different: I thought that was the point of assigning a DNS address to look at OpenDNS?"
No, in no way. These "DNS and IP addresses" are yours, not OpenDNS'. With configuring the OpenDNS resolver addresses you want to send your DNS queries to OpenDNS. With your DNS IP address OpenDNS associates your settings with your DNS queries.
To see what is possible and what not, post the complete plain text output of the following commands:
nslookup -type=txt which.opendns.com.
nslookup -type=txt debug.opendns.com. 208.67.220.220
What is the IP address from http://myip.dnsomatic.com/ ?
What message does http://welcome.opendns.com/ display?
-
The first one:
Server: dsmdc-dns-dts10.mcomdc.com
Address: 97.64.168.12which.opendns.com text =
"I am not an OpenDNS resolver."
opendns.com nameserver = auth3.opendns.com
opendns.com nameserver = auth1.opendns.com
opendns.com nameserver = auth2.opendns.com
auth1.opendns.com internet address = 208.69.39.2
auth2.opendns.com internet address = 67.215.92.66
auth3.opendns.com internet address = 208.69.39.2The second:
Server: dsmdc-dns-dts10.mcomdc.com
Address: 97.64.168.12 -
What is the purpose of putting static DNS addresses in the router? I had thought my problem was that the router was ignoring these and using it's own. But I also see that the OpenDNS Updater utility is coming up with a completely different addres (67.63.55.33), Where's that coming from?
-
"I am not an OpenDNS resolver."
You don't use OpenDNS yet.
"What is the purpose of putting static DNS addresses in the router?"
This is that you use OpenDNS for your DNS queries.
"I had thought my problem was that the router was ignoring these and using it's own."
Does it? Fill the three Static DNS fields under the DHCP section with three addresses from: 208.67.222.222, 208.67.220.220, 208.67.222.220, 208.67.220.222.
If you don't have success doing so, try to flash your router with the original Linksys/Cisco firmware for your router model. It should work with this."But I also see that the OpenDNS Updater utility is coming up with a completely different addres (67.63.55.33),"
If you don't use OpenDNS, the OpenDNS Updater doesn't have any use. Forget and ignore it until then.
"Where's that coming from?"
I don't like to repeat me. Didn't I tell that it's your ISP?
-
I the DNS settings as you suggested (I have done this before according to the OpendDNS instructions) but still get the 'you are not using OpenDNS' message when I try testing it. Should my router status page be showing the OpenDNS DNS addresses you gave me or the ones from my ISP. It still shows the ones given out by my ISP.
-
"I the DNS settings as you suggested (I have done this before according to the OpendDNS instructions) but still get the 'you are not using OpenDNS' message when I try testing it. "
It seems your ISP redirects your DNS queries to their DNS service. Post the output of this command:
nslookup -type=txt which.opendns.com. 208.67.220.220"Should my router status page be showing the OpenDNS DNS addresses you gave me or the ones from my ISP. It still shows the ones given out by my ISP."
As you configured the OpenDNS resolver addresses on the LAN (DHCP) side, the status page http://ui.linksys.com/files/WRT110/1.0.05/StatusRouterDHCP.htm will still show the ISP's DNS server addresses. However, your devices will show the OpenDNS resolver addresses.
-
Thanks that sheds a little light for me. Here's the output of the nslookup cmd:
Server: resolver2.opendns.com
Address: 208.67.220.220which.opendns.com text =
"7.chi"
I also did an ipconfig /all and it looks like my ISP as well as OpenDNS's is listed.
Windows IP Configuration
Host Name . . . . . . . . . . . . : kwilde-hp
Primary Dns Suffix . . . . . . . : aisdom.tld
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : aisdom.tld
BelkinEthernet adapter Local Area Connection 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connection
Physical Address. . . . . . . . . : 2C-44-FD-66-95-53
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : YesWireless LAN adapter Wireless Network Connection 4:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #2
Physical Address. . . . . . . . . : 3C-A9-F4-5A-ED-75
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : YesWireless LAN adapter Wireless Network Connection 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
Physical Address. . . . . . . . . : 3C-A9-F4-5A-ED-75
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : YesWireless LAN adapter Wireless Network Connection 2:
Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : Intel(R) Centrino(R) Ultimate-N 6300 AGN
Physical Address. . . . . . . . . : 3C-A9-F4-5A-ED-74
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::95e0:b2c8:f866:8438%21(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.111(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, December 30, 2013 7:28:24 AM
Lease Expires . . . . . . . . . . : Tuesday, December 31, 2013 7:28:24 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 524069364
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-89-A8-61-64-31-50-7D-62-A6
DNS Servers . . . . . . . . . . . : 97.64.168.12
97.64.183.165
192.168.1.1
208.67.222.222
208.67.220.220
208.67.222.220
NetBIOS over Tcpip. . . . . . . . : EnabledTunnel adapter isatap.Belkin:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : YesTunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:14d5:36c6:3f57:fe90(Preferred)
Link-local IPv6 Address . . . . . : fe80::14d5:36c6:3f57:fe90%30(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled -
""7.chi""
No, your ISP is not redirecting your DNS queries, and you can use OpenDNS. You will be using the OpenDNS Chicago location.
DNS Servers . . . . . . . . . . . : 97.64.168.12
97.64.183.165
192.168.1.1
208.67.222.222
208.67.220.220
208.67.222.220Oops, yes, beside the OpenDNS resolver addresses there are two ISP DNS resolver addresses and the router's IP address. Weird enough. You must eliminate all except the OpenDNS addresses. If the router doesn't do its job orderly, as seem to be the case, then you must configure the OpenDNS resolver addresses manually on the computer as outlined here: https://store.opendns.com/setup/computer/
-
I really need to use the router as with at least six internet devices in the house (computers, gaming consoles, phones, etc) it's the only practical way. Do you think using another router would fix things? I have a couple of others I could try if you think its a reasonable possibility.
-
I changed routers to a D-Link DIR-625 and got it working (at least as far as the internetbadguys.com link is concerned). Apparently the Linksys WRT110 is not compatible with your service. There's not info on your help page for the DIR-625 but the setup is pretty straight forward. Thanks a lot for your help.
-
"Apparently the Linksys WRT110 is not compatible with your service."
That's not my service. I'm a user like you.
And this would be a wrong point of view. A malfunction of a router has nothing to do with compatibility. This device would have the same problem with any 3rd party DNS resolver addresses, not just with OpenDNS. The device offers a function (entering static resolver addresses) which simply does not work. Refer to Linksys support because of this firmware bug.
Please sign in to leave a comment.
Comments
14 comments