<div dir="ltr"><br><br><div class="gmail_quote">On Thu, Jul 24, 2008 at 8:48 PM, Carlos Carvalho <<a href="mailto:carlos@fisica.ufpr.br">carlos@fisica.ufpr.br</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Brad Morgan (<a href="mailto:b-morgan@concentric.net">b-morgan@concentric.net</a>) wrote on 24 July 2008 14:15:<br>
<div class="Ih2E3d"> >After playing with dnsmasq log-queries for a while, I think there should be<br>
>a signal that dynamically toggles this option. Stopping and starting dnsmasq<br>
>doesn't work because it clears the cache and that's what I'm trying to<br>
>discover... Is the wrong answer coming out of cache or is it coming from the<br>
>DNS servers themselves and if so, which one if I have more than one to<br>
>choose from.<br>
</div>[removed]<br>
<div class="Ih2E3d"> >I'd rather not leave log-queries on all the time as it generates lots of log<br>
>entries but I would like to turn it on when I have a problem (and off again<br>
>after resolving the issue).<br>
<br>
</div>If you turn logging off after solving it there's no problem in<br>
restarting dnsmasq without the cache. The benefit of the signal would<br>
be only to preserve the cache.</blockquote><div><br>Evidently, it is turning logging *on* that presents the problem, because you can get no information about the state of the cache before dnsmasq was reloaded to enable logging. <br>
</div></div><br></div>