OpenDNS works, and then stops working overnight

dougw01

February 16, 2017 14:44

I recently started using OpenDNS (family version so .123 DNS not .220)

Arris Surfboard (SGB6700-AC) purchased from Amazon connected to TWC/Spectrum cable here in San Diego California

After logging into Router and changing DNS server, OpenDNS is 'working' [meaning I can get a greencheck mark from OpenDNS.com/welcome and sites are blocked with my customized message).

Then I go to bed, wake up in the morning and now it is not working.

My IPv4 address to the internet has not changed. And when I log into my router the DNS settings are still the same.

I noticed this morning that the IPv4 DNS servers are not settable (see pic below)

Any ideas?

Comments

4 comments

dougw01 February 16, 2017 15:13

I kept on working on this after I posted this question....

Changed router setttings to 220. Rebooted router. Opendns not working.

rebooted compter that was doing the settings, and now OpenDNS is working, both on this computer AND on others on the network

I will monitor during the day, but I still expect the settings to 'magically' change at somepoint, so still looking for ideas.

0

Comment actions Permalink
rotblitz February 16, 2017 18:43
As soon as you face this problem again, i.e. http://welcome.opendns.com/ indicating you're not using OpenDNS, copy & paste the complete plain text outputs of the following diagnostic commands to here:
```
nslookup -type=txt debug.opendns.com.
nslookup whoami.akamai.net.
netsh interface ipv4 show config
netsh interface ipv6 show dns
```
I may then see what the problem is.
0

Comment actions Permalink
dougw01 February 17, 2017 00:58

Thanks. Things were working all day until sometime in the last hour or so....

below is cut'n'paste of commands. note that I tried with and without . at end of first 2

When i look at the router settings, the IPv4 servers are now 209.18.47.61 and.62

There is still the setting to 'use below' settings, which are still the OpenDNS settings.

Thanks for the help

C:\Users\Doug>nslookup -type=txt debug.opendns.com.
Server: dns-cac-lb-02.rr.com
Address: 209.18.47.62

*** dns-cac-lb-02.rr.com can't find debug.opendns.com.: Non-existent domain

C:\Users\Doug>nslookup -type=txt debug.opendns.com
Server: dns-cac-lb-02.rr.com
Address: 209.18.47.62

*** dns-cac-lb-02.rr.com can't find debug.opendns.com: Non-existent domain

C:\Users\Doug>
C:\Users\Doug>
C:\Users\Doug>nslookup whoami.akamai.net.
Server: dns-cac-lb-02.rr.com
Address: 209.18.47.62

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

C:\Users\Doug>nslookup whoami.akamai.net
Server: dns-cac-lb-02.rr.com
Address: 209.18.47.62

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

C:\Users\Doug>netsh interface ipv4 show config

Configuration for interface "Local Area Connection"
DHCP enabled: Yes
IP Address: 192.168.0.2
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: 209.18.47.62
209.18.47.61
Register with which suffix: Primary only
WINS servers configured through DHCP: None

Configuration for interface "Wireless Network Connection"
DHCP enabled: Yes
InterfaceMetric: 25
DNS servers configured through DHCP: 209.18.47.61
209.18.47.62
Register with which suffix: Primary only
WINS servers configured through DHCP: None

Configuration for interface "Local Area Connection* 2"
DHCP enabled: Yes
InterfaceMetric: 25
DNS servers configured through DHCP: None
Register with which suffix: Primary only
WINS servers configured through DHCP: None

Configuration for interface "Local Area Connection* 3"
DHCP enabled: Yes
InterfaceMetric: 25
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

C:\Users\Doug>netsh interface ipv6 show dns

Configuration for interface "Local Area Connection"
DNS servers configured through DHCP: None
Register with which suffix: Primary only

Configuration for interface "Wireless Network Connection"
DNS servers configured through DHCP: None
Register with which suffix: Primary only

Configuration for interface "Local Area Connection* 2"
DNS servers configured through DHCP: fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Register with which suffix: Primary only

Configuration for interface "Local Area Connection* 3"
DNS servers configured through DHCP: fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Register with which suffix: Primary only

Configuration for interface "Loopback Pseudo-Interface 1"
Statically Configured DNS Servers: fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Register with which suffix: Primary only

Configuration for interface "isatap.{8BF7B662-1D91-46CC-B9D4-74AA4DF90A20}"
Statically Configured DNS Servers: None
Register with which suffix: None

Configuration for interface "Local Area Connection* 13"
Statically Configured DNS Servers: None
Register with which suffix: None

C:\Users\Doug>

C:\Users\Doug>

C:\Users\Doug>

0

Comment actions Permalink
rotblitz February 17, 2017 14:48 (Edited February 17, 2017 14:50)

Server: dns-cac-lb-02.rr.com
Address: 209.18.47.62

You used your ISP's DNS service at this time. Your router doesn't propagate the configuration via DHCP you have configured on it. So it's clearly a router bug. You'll want to refer to your router's support. Maybe an upgrade to a newer firmware can help too.

As a workaround for the time being, configure the OpenDNS resolver addresses also on the end user devices. Then you'll use OpenDNS instantly, not just randomly, on these devices.

0

Comment actions Permalink

Please sign in to leave a comment.

Comments

Didn't find what you were looking for?