Bug#605060: dnsmasq preserves cache across interface changes

2010-11-26 Thread Daniel Jacobowitz
Package: dnsmasq
Version: 2.55-2
Severity: normal

I am using resolvconf and dnsmasq to handle internal DNS servers for
our VPN.  When openconnect creates the tun0 interface, it adds the
internal nameservers using resolvconf.  resolvconf modifies dnsmasq's
configuration file, and dnsmasq rereads it.  But my IRC client fails
to reconnect to the internal server at this point, because the
negative lookup has been cached - the IRC server's hostname is only
valid inside the VPN.

I don't see any option to make dnsmasq clear its cache when the VPN
comes up other than restarting dnsmasq entirely.  It'd be nice if I
could make this happen automatically when dnsmasq rereads the
resolv.conf file.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dnsmasq depends on:
ii  adduser   3.112+nmu1 add and remove users and groups
ii  dnsmasq-base  2.55-2 A small caching DNS proxy and DHCP
ii  netbase   4.43   Basic TCP/IP networking system

dnsmasq recommends no packages.

Versions of packages dnsmasq suggests:
ii  resolvconf1.46   name server information handler

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#605060: dnsmasq preserves cache across interface changes

2010-11-26 Thread Simon Kelley
Daniel Jacobowitz wrote:
 Package: dnsmasq
 Version: 2.55-2
 Severity: normal
 
 I am using resolvconf and dnsmasq to handle internal DNS servers for
 our VPN.  When openconnect creates the tun0 interface, it adds the
 internal nameservers using resolvconf.  resolvconf modifies dnsmasq's
 configuration file, and dnsmasq rereads it.  But my IRC client fails
 to reconnect to the internal server at this point, because the
 negative lookup has been cached - the IRC server's hostname is only
 valid inside the VPN.
 
 I don't see any option to make dnsmasq clear its cache when the VPN
 comes up other than restarting dnsmasq entirely.  It'd be nice if I
 could make this happen automatically when dnsmasq rereads the
 resolv.conf file.
 

From man dnsmasq

  --clear-on-reload
   Whenever /etc/resolv.conf is re-read, clear the DNS cache.  This
   is useful when new nameservers may have different data than that
   held in cache.

Unless I've misunderstood, that's what you want. (Note that
/etc/resolv.conf here stands for any file that dnsmasq is reading to
get the nameservers.)


Cheers,

Simon.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org