Some observations (which might help other people trying to achieve similar goals or help me if someone on the list has found better ways to accomplish this).<div><br></div><div>One server which handles DNS, DHCP (dnsmasq) and other services (cups, ssh, ...).</div>
<div><br></div><div>When it comes to configuring dnsmasq the "problems" start when one tries to make the server reachable by other computers (by hostname) and when the server tries to serve it's own dns queries.</div>
<div><br></div><div>1. server hostname</div><div>- "/etc/hosts" : might not cut it because it might be overwritten by some other service</div><div>- "dhcp-host" dnsmasq option : does not work for providing the "own" host name</div>
<div><br></div><div>one can use "no-host" and/or "addn-hosts" dnsmasq option to provide the own host name</div><div><br></div><div>2. nameserver</div><div>- "/etc/resolv" : might not cut it because it might be overwritten by some other service</div>
<div>- "server" dnsmasq option : does not work for providing the "own" nameserver name</div><div>- "resolv-file" dnsmasq option : does not work for providing the "own" nameserver name</div>
<div><br></div><div>the only option seems to be to create a "/etc/resolv.conf" file before starting (or restarting) dnsmasq</div><div><br></div><div>If my findings are wrong please enlighten me :-), otherwise I hope this summary is of some use to someone.</div>
<div><br></div><div>cheers,</div><div>wim</div>