So the cleanest solution is setting Used Domain to LAN/WLAN and don't add the domain-entry into Additional DNSMasq Options. The problem is: If you use DNSMasq as DHCP Server the LAN Domain is already written into DNSMasq conf and if you add it to Additional DNSMasq Options it's been added twice and (quoting frater:) the thing goes berserk. Towelie 15:57, 23 November 2010 (CEST)įor me (with WRT350N-15508std) the above description didn't work (could resolve names in LAN only - you may check my topic). Pick something other than ".local" for your domain. You can get strange results like nslookup working while pings fail. But "local" is not a good idea for a local domain, because multicast / ZeroConf uses ".local" for its own purposes. In order for expand-hosts to work, you need a domain=local line in there as well. In the below screenshot, there are a couple of mistakes. Assuming your LAN domain is called 'lan', put the following lines in the "additional DNSMasq options" field: Update: For DNSMasq Options, I found the explanation below confusing it's much simpler than it sounds. You can add static allocations the same way as when you're using DHCPd.
Additional DNSMasq Options = Add your domain as a local search domain, add expand-hosts option.Use DNSMasq for DHCP = Checked (only present if running a build Services.This is the easiest way to setup DNSMasq as DHCP Server 3.11 Using DNSMasq for Router advertisements (IPv6).3.7 Denying DHCP service to specific MAC addresses.