Johannes Stezenbach wrote:
Package: dnsmasq
Version: 2.33-1+b1
Severity: normal
Tags: patch
I have to use a VPN connection (using vpnc) for some of my work.
The same hostname might then resolve to a different IP address
when the VPN connection is up or down.
resolvconf correctly updates /var/run/dnsmasq/resolv.conf,
and dnsmasq recognizes the change (logged to syslog).
However, dnsmasq continues to return stale information
from its cache.
The attached patch sends SIGHUP to dnsmasq after the resolv.conf
change to clear the cache.
I wonder if this is generally the right thing to do, but
it fixes my problem. I think ideally dnsmasq should have
a config option to clear the cache automatically when it
detects a resolv.conf change.
An interesting problem: in almost all cases, re-reading resolv.conf will
result in an unchanged set of nameservers, or another set which give
exactly the same view of the DNS, so clearing the cache is not the right
thing to do. On the other hand, clearing the cache won't break anything,
and the extra cost of re-loading entries in negligable in most cases.
A dnsmasq config option gives the user choice (and will work without
resolvconf) but it add yet another option onto a now enormous list.
A quandary.....
Simon.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
