DNS Order on client devices

[TheRealMaxey]

I'm having an issue where my client devices are going directly to OpenDNS servers first, and then my router for DNS queries. I can't figure out what settings I screwed up to make it this way...

WAN Settings - http://puu.sh/lbISm/22286d960c.png

LAN Settings - http://puu.sh/lbITU/9c39bb476b.png

Client ipconfig output - http://puu.sh/lbIWs/a07485a75b.png

I do not have any of the clients hardcoded to DNS, they just use what they get from the router. In this case, going directly to OpenDNS is bypassing the adblocking through the hosts file on the router.

Any thoughts?

EDIT: These are for locally connected clients, not VPN.

 

[coxhaus]

I noticed a couple of unusual things in my mind on the settings. First you have no default gateway defined in the ASUS router and yet the client is showing up with a default gateway. Second you have a setting for not connecting to the DNS server. It may be my lack of ASUS knowledge.

Why not put your local DNS server on the WAN side DNS with a connecting setting. Setup your local DNS server with a forwarder to your OpenDNS servers. Let the DNS server handle resolving IP addresses. Let the router cache your DNS entries.

 

[TheRealMaxey]

So here's the wrinkle, the ASUS router is providing the Local DNS. So in this case, here's how it should go from a DNS lookup standpoint: Client-->Router-->OpenDNS-->Internet

However, I'm finding that it's going: Client-->OpenDNS-->Internet

The latter situation bypasses any content filtering on the router and I am baffled as to what combination of settings will get me where I need to be.

 

[ColinTaylor]

It looks like you've either discovered a bug or have some corrupted NVRAM values. What you have should work as you want but obviously isn't.

Try setting LAN > DHCP Server > DNS Server 1 & 2 to be blank and "Advertise router's IP in addition to user-specified DNS" to Yes.

That should be more or less the defaults and the same as I have. Reboot the router and then your PC. Check the PC's DNS setting again. It should be just 10.1.1.1

 

[TheRealMaxey]

Just tried exactly as you said, followed by a reboot of the router, ip release on the client, and then a client reboot. Same result. How do I clear the NVRAM, or am I stuck with a reset?

 

[ColinTaylor]

You can use John's utility to backup your settings: http://www.snbforums.com/threads/user-nvram-save-restore-utility-r22.19521/

Instructions for clearing NVRAM are here (How do I do a factory default reset?): http://forums.smallnetbuilder.com/showthread.php?t=19521

If that doesn't work, try temporarily changing your routers IP address back to the default of 192.168.1.1 instead of 10.1.1.1. Then test again. I've come across cases where some of the routers functions can't cope with being changed from the default.

 

[john9527]

Just as a double check....you don't have anything set in DNS Filter, correct?

 

[ColinTaylor]

Also, after doing a factory reset and before restoring your settings, just do the absolute minimum changes that allow you to access the router. Then check the client again to see if it is picking up 192.168.1.1 as its only DNS.

 

[ColinTaylor]

Just as a double check....you don't have anything set in DNS Filter, correct?

The problem appears to be that DHCP is pushing out 3 DNS values to the client: http://puu.sh/lbIWs/a07485a75b.png