Package: dnsmasq
Version: 2.66-3
Severity: wishlist
When NetworkManager controls dnsmasq it configures dnsmasq to route VPN
domain name lookups to the VPN nameserver.
It should be possible to implement this for dnsmasq server too.
Suppose the VPN client has registered the following record called
'tap0.vpnclient'.
search abc.com
nameserver 172.17.24.1
Earlier the following 'eth0.dhclient' record was already registered.
search myhome.nu
nameserver 192.168.1.1
Dnsmasq's resolvconf hook script could direct dnsmasq to do the equivalent
of
server=/abc.com/172.17.24.1
server=192.168.1.1
First, the "whether". Is this a desirable feature?
Second, the "how". Currently, dnsmasq's resolvconf hook script writes a
resolv.conf-format file at /var/run/dnsmasq/resolv.conf. To implement the
new functionality, I take it that the hook script would have to depart from
that. It would have to write a configuration file and restart dnsmasq, or
send the information to dnsmasq via D-Bus, as NetworkManager does. Am I
right in assuming that the latter would be better?
Let the discussion begin. :)
--
Thomas
