Page 2 of 2

Re: DHCP serving wrong DNS servers

Posted: Sun Sep 29, 2013 12:24 pm
by gargoylepio
Same problem here, I already have an internal network, with an internal DNS server (to serve some internal only domains) and a DHCP server.

The gui of gargoyle is rather nice, but it appears to only target certain common situations where the wifi router it concerns, will have a very central role in DHCP and DNS.

I found these symptoms:

- during DHCP responses, the router's IP number is always promoted as being the DNS server, regardless of what you configure in the gargoyle interface
- even when I configure my internal DNS server as 'custom DNS server', lookups for my internal domain don't work

I am quite new to gargoyle and I am wondering what the usability is for more complex network setups? (e.g. L2/L3 switch, guest network, private network, mdns stuff, ..)

I am going to dive more into OpenWRT cli now, presumably that is going to be the solution for me.

Re: DHCP serving wrong DNS servers

Posted: Sat Mar 01, 2014 1:18 pm
by drueter
The name server addresse(s) used for DNS resolution by the router is not automatically used as the nameserver addresse(s) provided to DHCP clients.

The router defaults to serving up the router's address as the DNS server when DHCP clients request an IP address.

To change the DNS server address that will be provided to DHCP clients, you must edit /etc/config/dhcp and under "config dhcp 'lan'" add:

list 'dhcp_option' '6,xxx.xxx.xxx,yyy.yyy.yyy'

where xxx.xxx.xxx and yyy.yyy.yyy are the primary and secondary DNS servers you wish to send to DHCP clients. Remember to reboot (or restart dnsmasq) when done.

See the full instructions at http://wiki.openwrt.org/doc/howto/dhcp.dnsmasq