[Dnsmasq-discuss] how to handle the local domain (A, PTR)

[Simon Kelley]

On 27/07/12 08:11, Wojtek Swiatek wrote:
> Hello,
>
> I set up dnsmasq on my home network to replace the isc/bind legacy
> system :) when changing the architecture. The setup relies on a debian
> which acts as the router/firewall/"master of all truth" (DNS, ntp,
> ...):
> - an ADSL access to Internet with the public IP assigned to eth1
> - a wired network 192.168.0.0/24 bound to eth0 (which has the
> 192.168.0.10 address)
> - a wired network 192.168.1.0/24 bound to wlan3 (which has the
> 192.168.1.10 address)
> - the domain name for the internal network is "home"
> - firewalling is handled by shorewall
>
> The dnsmasq configuration is:
>
> domain-needed
> bogus-priv
> local=/home/
> expand-hosts
> domain=home
> dhcp-range=eth1,192.168.0.70,192.168.0.150,240h,set:lan
> dhcp-range=wlan3,192.168.1.10,192.168.1.50,240h,set:wifi
> dhcp-option=42,0.0.0.0
> dhcp-option=27,1
> dhcp-option=19,0           # option ip-forwarding off
> dhcp-option=44,0.0.0.0     # set netbios-over-TCP/IP nameserver(s) aka
> WINS server(s)
> dhcp-option=45,0.0.0.0     # netbios datagram distribution server
> dhcp-option=46,8           # netbios node type
> dhcp-option=252,"\n"
> dhcp-option=vendor:MSFT,2,1i
> dhcp-authoritative
>
>
> What works:
> - clients in the subnets (both wired and wireless) get IP addresses
> via DHCP in the expected ranges
> - external (Internet = forwarded) DNS resolution works for these
> clients and for the server
>
> What does not work: the "home" domain name does not seem to be handled:
>    * /etc/hosts has a
>      192.168.0.10 server.home
>     entry which is not used, ie. "dig server" does not return the name,
> "dig server.home" does not either.
>    * PTR records for DHCP-assigned names are not there
>
> I am sure that this is something obvious but I am brand new to dnsmasq
> and would appreciate very much any pointers.
>
> Thank you,
> Wojtek
>


It's not obvious to me what the problem is. The first thing to do is to set

log-queries

in /etc/dnsmasq.conf and look to see what DNS queries are being 
generated, if they're getting to dnsmasq, and what it's doing with them.

Cheers,

Simon.