OpenDNS not working

meathead40

February 07, 2014 19:45

I had OpenDNS working briefly, then it stopped working. Can someone advise?

nslookup -type=txt debug.opendns.com

C:\Users\Tim>nslookup -type=txt debug.opendns.com
Server: mydlink
Address: 192.168.0.1

*** mydlink can't find debug.opendns.com: Non-existent domain

Comments

9 comments

rotblitz February 08, 2014 13:07

"*** mydlink can't find debug.opendns.com: Non-existent domain"

This shows that you don't use OpenDNS yet. You must configure only OpenDNS resolver addresses. From "mydlink" I would think you intend to do this on your D-Link router.
https://store.opendns.com/setup/router/D-Link

0

Comment actions Permalink
meathead40 February 08, 2014 17:01
Yes, I have my dlink router set up to use the namespaces:
- 208.67.222.222
- 208.67.220.220
The strange thing is that it worked for about 5 minutes (OpenDNS was blocking websites)... then I registered for an account and registered my IP address with OpenDNS. At that point, it stopped working, so I removed my IP address from OpenDNS, and it still didn't work. I tried rebooting machine and router multiple times. I can clearly see that the DNS is set in the router settings to use OpenDNS, but it doesn't 'grab' for some reason. Not sure if my ISP Cox has to do with it?

Please let me know what I can do, I really want to utilize the protections provided by the family guard.
0

Comment actions Permalink
rotblitz February 09, 2014 14:51

"Not sure if my ISP Cox has to do with it?"

Could well be that your ISP redirects your DNS queries to their own DNS service. Check it:

nslookup -type=txt which.opendns.com. 208.67.220.220

If this returns "I am not an OpenDNS resolver", then your ISP redirects your DNS queries.

0

Comment actions Permalink
meathead40 February 09, 2014 16:25

Here is the result, doesn't look like Cox is an issue.

C:\Users\Tim>nslookup -type=txt which.opendns.com. 208.67.220.220
Server: resolver2.opendns.com
Address: 208.67.220.220

Non-authoritative answer:
which.opendns.com text =

"11.lax"

0

Comment actions Permalink
rotblitz February 09, 2014 16:30

No, your ISP does not redirect your DNS queries. So it must be something else like using another DNS service in addition.

Now post the complete plain text output of the following command:

ipconfig /all

0

Comment actions Permalink
meathead40 February 09, 2014 16:32

Here it is:

C:\Users\Tim>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DellR4
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ph.cox.net

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : ph.cox.net
Description . . . . . . . . . . . : Realtek RTL8188CU Wireless LAN 802.11n US
B 2.0 Network Adapter
Physical Address. . . . . . . . . : 00-E0-4C-BB-1E-2B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::35d8:e372:e2d9:e9d8%18(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.123(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, February 07, 2014 12:24:47 PM
Lease Expires . . . . . . . . . . : Sunday, February 16, 2014 9:22:14 AM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 385933388
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-57-63-CB-84-8F-69-F5-02-0E

DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : ph.cox.net
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 84-8F-69-F5-02-0E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.ph.cox.net:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : ph.cox.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel 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:90d7:3ca7:1e19:3f57:ff84(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::3ca7:1e19:3f57:ff84%13(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

0

Comment actions Permalink
rotblitz February 09, 2014 16:37

"DNS Servers . . . . . . . . . . . : 192.168.0.1"

This points to your router only which is ok. So everything is with your router. Post the complete output of:

nslookup -type=txt which.opendns.com.

Can you also post a screen shot of your router's page where you configured the OpenDNS resolver addresses.

0

Comment actions Permalink
meathead40 February 10, 2014 03:16

C:\Users\Tim>nslookup -type=txt which.opendns.com
Server: mydlink
Address: 192.168.0.1

Non-authoritative answer:
which.opendns.com text =

"I am not an OpenDNS resolver."

Here is a screenshot of my router: http://prntscr.com/2r502y

Note that I manually set the host name... not sure if that matters. Appreciate your help.

0

Comment actions Permalink
rotblitz February 10, 2014 07:10

The hostname does not really matter.

It seems the settings on your router do not take effect. Try with another firmware version, or refer to D-Link support.

0

Comment actions Permalink

Please sign in to leave a comment.

The OpenDNS Community has moved!

Comments