/etc/resolv.conf always populates with router address regardless of "Local DNS" setting

[DaveTheNerd]

Using WRT600N standard build 11942M. The router sets itself to be it's own DNS server even if it's not capable of handling those requests.

I have the router set in DHCP Forwarder mode, and also set the "Local DNS" to another machine internal to the network. Still, the router itself tries to use its own address for DNS. The only way around this issue is to edit the /etc/resolv.conf file on each boot, or to enable DNSMasq and set a listen-address (to the router) and a server address (to the external server).

it would seem logical to me that whatever's entered into "Local DNS" on the Setup->Basic Setup sheet would be reflected in /etc/resolv.conf (If I'm wrong, just let me know).

[BrainSlayer]

unless you disable dnsmasq, this behaviour is correct

[DaveTheNerd]

Ah, ok. Will test.

But even still: shouldn't dnsmasq have a listen-address set to the router's IP address by default instead of just on 127.0.0.1?

The default dnsmasq settings (of answering only on 127.0.0.1) leave the router with no DNS for itself (which screws up things like DDNS, NTP client, incoming PPTP connections).

[BrainSlayer]

dnsmasq uses /tmp/resolv.dnsmasq entries for resolving the addresses. this file is normally filled up with your dns entries. if you didnt configured dns, it cannot resolv it for sure

[DaveTheNerd]

I think I've confused the issue. It's not that dnsmasq doesn't resolve properly. It works fine when it's properly accessed.

The problem is that, with DHCP set to "Forwarder" it seems dnsmasq is only set to answer on 127.0.0.1, not the 192.168.x.x address of the router. Therefore dnsmasq doesn't answer queries since /etc/resolv.conf points to 192.168.x.x instead of 127.0.0.1. Setting a

listen-address=192.168.x.x,127.0.0.1

in dnsmasq.conf solves this problem, but it must be done separately on each boot since it's not the default.