<div dir="ltr">After considering the benefit of dnsmasq making sure that the right nameservers are used, I'm sold.<br>For debugging (I'm not sure if dnsmasq is the bottleneck for DNS queries), what option should I enable to generate as low overhead as possible and direct the DNS clients' requests directly to upstream nameservers?<br>
<br>However, I consider cache=0 -> IP dnsmasq server in client resolv.conf a bug as it stops DNS working completely.<br><br>Regards,<br><br>Ondrej Grover<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Sun, Feb 17, 2013 at 5:19 PM, Simon Kelley <span dir="ltr"><<a href="mailto:simon@thekelleys.org.uk" target="_blank">simon@thekelleys.org.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 16/02/13 12:03, Chris Wilson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Ondrej,<br>
<br>
On Sat, 16 Feb 2013, Ondřej Grover wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thank you, this would solve my problem if the nameservers listed in<br>
/etc/resolv.conf on the server didn't change, but they do (the server<br>
is more like a router, acquires IP and dns info from my ISP via DHCP).<br>
<br>
As dnsmasq is able to read /etc/resolv.conf on the server, I was<br>
hoping there would be a way for dnsmasq to propagate the nameservers<br>
listed there automagicaly to its clients.<br>
</blockquote>
<br>
If the DNS servers listed there change, there's no way to inform the<br>
DHCP clients of that. If they continue to use the old servers and those<br>
servers stop working, the clients will fail.<br>
<br>
Just use dnsmasq to proxy to the DNS servers already. dnsmasq will<br>
automatically start forwarding queries to new servers when the list<br>
changes. And it will cache queries for you, so it will be faster.<br>
<br>
<br>
</blockquote>
<br>
I'd echo Chris's observation here: dnsmasq's orignal raison d'etre was to allow the upstream nameserver to change without needing to undergo the problematic process of propogating that to all the clients on the local network.<br>
<br>
It probably makes sense that dnsmasq-dhcp should not advertise itself by default as the DNS server of the dnsmasq-dns is disabled with port=0, (or port= anything other than 53, for that matter.)<br>
<br>
Cheers,<br>
<br>
Simon.<br>
<br>
______________________________<u></u>_________________<br>
Dnsmasq-discuss mailing list<br>
<a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank">Dnsmasq-discuss@lists.<u></u>thekelleys.org.uk</a><br>
<a href="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss" target="_blank">http://lists.thekelleys.org.<u></u>uk/mailman/listinfo/dnsmasq-<u></u>discuss</a><br>
</blockquote></div><br></div>