[Bug 1042275] Re: dnsmasq should not register 127.0.0.1 with resolvconf if it's not listening on lo

[Thomas Hood]

Currently it's the initscript that talks to resolvconf.  If we want the
initscript to implement the behavior requested here (i.e., "register
127.0.0.1 with resolvconf if and only if dnsmasq is listening on lo")
then the initscript will have to understand dnsmasq's configuration
files. That's asking too much from an initscript.

Dnsmasq should be enhanced so that the dnsmasq process talks to
resolvconf. The process knows whether or not it's listening on the
loopback address.

Furthermore, the process knows exactly which addresses it's binding; so
if it's listening on 127.0.0.2 it can register 127.0.0.2 with
resolvconf. Nice.

Furthermore, the process knows when it has been terminated, even if it's
not the initscript that's sent the signal, so it can de-register its
listen address with resolvconf. Nice.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1042275

Title:
  dnsmasq should not register 127.0.0.1 with resolvconf if it's not
  listening on lo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1042275/+subscriptions