D-Link DIR-882

lesliedbruce

April 19, 2018 02:04

I can't get opendns to work. Disabling DNS relay kills the network.

Suggestions?

Comments

8 comments

rotblitz April 19, 2018 18:12 (Edited April 19, 2018 18:17)

Can you post a screen shot of the router page where you configured OpenDNS. In case you have IPv6 connectivity, also a screen shot from the IPv6 configuration page.

0

Comment actions Permalink
lesliedbruce April 19, 2018 18:20 (Edited April 19, 2018 18:22)

IP address pixilated for privacy. Thanks for any input you may have. IPv6 blank.

0

Comment actions Permalink
rotblitz April 19, 2018 18:25 (Edited April 19, 2018 19:55)
This looks fine. Now copy & paste the complete plain text output of the following diagnostic commands to here:
```
nslookup -type=txt debug.opendns.com. 208.67.220.220
nslookup -type=txt which.opendns.com.
nslookup whoami.akamai.net.
netsh interface ipv4 show config
```
0

Comment actions Permalink
lesliedbruce April 19, 2018 18:28

Input each line separately in Win 10 cmd?

0

Comment actions Permalink
lesliedbruce April 19, 2018 18:32

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

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

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

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

C:\Users\SYSTEM_01>nslookup -type=txt which.opendns.com.
Server: resolver1.opendns.com
Address: 208.67.222.222

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

        "I am not an OpenDNS resolver."

C:\Users\SYSTEM_01>nslookup whoami.akamai.net.
Server: resolver1.opendns.com
Address: 208.67.222.222

Non-authoritative answer:
Name:    whoami.akamai.net
Address: 71.14.220.248

Configuration for interface "Ethernet"
DHCP enabled: Yes
IP Address: 192.168.0.188
Subnet Prefix: 192.168.0.0/24 (mask 255.255.255.0)
Default Gateway: 192.168.0.1
Gateway Metric: 0
InterfaceMetric: 25
DNS servers configured through DHCP: 208.67.222.222
208.67.220.220
Register with which suffix: Primary only
WINS servers configured through DHCP: None

Configuration for interface "Bluetooth Network Connection"
DHCP enabled: Yes
InterfaceMetric: 65
DNS servers configured through DHCP: None
Register with which suffix: Primary only
WINS servers configured through DHCP: None

Configuration for interface "Loopback Pseudo-Interface 1"
DHCP enabled: No
IP Address: 127.0.0.1
Subnet Prefix: 127.0.0.0/8 (mask 255.0.0.0)
InterfaceMetric: 75
Statically Configured DNS Servers: None
Register with which suffix: Primary only
Statically Configured WINS Servers: None

0

Comment actions Permalink
rotblitz April 19, 2018 19:54 (Edited April 19, 2018 20:12)

Your problem has nothing to do with your router.

It looks like as if your ISP Charter redirects your DNS traffic to their own DNS service. You may want to contact them to ask for opting out from this DNS traffic redirection. Else you can try to circumvent this restriction with using https://dnscrypt.info/implementations/

0

Comment actions Permalink
lesliedbruce April 19, 2018 22:39

You were correct. I called up my ISP and they told me that they were having some dns problems a while ago and they had to create a custom script. They forgot to remove it. They removed it now, and now everything in OpenDNS works.

Much thanks.

0

Comment actions Permalink
rotblitz April 19, 2018 23:26

Welcome! Glad to hear!

0

Comment actions Permalink

Please sign in to leave a comment.

Comments

Didn't find what you were looking for?