Posted: Sun Mar 25, 2012 18:47 Post subject: "Local DNS" option is for uDHCPd, not for DNSMasq
Good people of the forum, please consider this. It seems there is some confusion between options
Setup : Basic Setup : Network Address Server Settings (DHCP) : "Use DNSMasq for DNS" (checkbox)
Services : Services : DNSMasq : "Local DNS" (enable/disable radio buttons)
Of those two, I believe that "Use DNSMasq for DNS" is the only one relevant to DNSMasq, i.e., the "Local DNS" option does nothing for DNSMasq. On my routers (build 15230 mini), I have looked at /tmp/dnsmasq.conf and /tmp/resolv.dnsmasq, and I see no change in these files when changing the "Local DNS" option. I think I've tracked down the source of this. The nvram variable in question here is "dns_local", as can be seen in
and see that dns_local is used by uDHCPd but completely ignored by DNSMasq. Therefore, the "Local DNS" option is for uDHCPd and not DNSMasq.
Well, this is kind of funny, because if DNSMasq is disabled by these chechboxes/buttons,
Setup : Basic Setup : Network Address Server Settings (DHCP) : "Use DNSMasq for DHCP" (checkbox)
Setup : Basic Setup : Network Address Server Settings (DHCP) : "Use DNSMasq for DNS" (checkbox)
Services : Services : DNSMasq : "DNSMasq" (enable/disable radio buttons)
then the WebUI hides the "Local DNS" option at the only time that it is relevant, which is when uDHCPd must handle DNS. The code in udhcpd.c seems to show that uDHCPd does not load if "Use DNSMasq for DHCP" is checked, so there is no way to use DNSMasq for DHCP and use uDHCPd for DNS (not that you would want to do that).
As a first step to minimise this confusion, I believe the "Local DNS" option should be removed from the "DNSMasq" fieldset box on the Services page. Instead, it should show "Local DNS" and "Additional DHCPd Options" in a separate fieldset with the legend "uDHCPd", in the same way "DNSMasq Enable/Disable", "No DNS Rebind" and "Additional DNSMasq Options" are in a fieldset with the legend "DNSMasq".
i hope this i addressed. I have tried to use udhcpd instead of dnsmasq, partly because the dhcp lease times are then usefully displayed in the gui. the other option would be for the devs to fix the dnsmasq lease time display. these are old issues that seem to have been dropped; the solutions are apparently not complex and a little code cleanup could solve years of frustions.
does anyone have influence of knowledge about how to get these changes implemented?
i hope this i addressed. I have tried to use udhcpd instead of dnsmasq, partly because the dhcp lease times are then usefully displayed in the gui. the other option would be for the devs to fix the dnsmasq lease time display. these are old issues that seem to have been dropped; the solutions are apparently not complex and a little code cleanup could solve years of frustions.
does anyone have influence of knowledge about how to get these changes implemented?
Normally one would register on the Trac system for DD-WRT, and then raise a change-ticket there. However registrations currently appear to be disabled. The next best approach might be to find someone with existing Trac access and ask them to raise the ticket. To be perfectly honest though, I'm not sure how much time/effort the devs are devoting to raised tickets these days. I could be wrong but it almost seems as if they're following some sort of internalized priority list and providing very little visible responsiveness to what's being raised in the forums and Trac. _________________ Ubiquiti EdgeRouter Lite | Primary router
D-Link dgs-1100-08 smartswitch | Main VLAN-aware switch
Netgear R7000 #1 | Primary AP
Netgear R7000 #2 | AC-only client-bridge (office)
Asus RT-AC66U | AC-only client-bridge (HTPC)
Netgear WNDR3700v2 | client-bridge (basement)