I filed this because I thought that even if we don't decide to deal with
#959037 by means of "except-interface=lo", this is a change that would
be good to make anyway.
But on second thought, this would just be one hack on top of another.
Dnsmasq has several options governing which interfaces and addresses it
listens on and several different files (/etc/dnsmasq.conf,
/etc/init.d/dnsmasq, /etc/default/dnsmasq, /etc/dnsmasq.d/*) that can
affect the option list. To be completely correct the initscript would
have to read all these configuration files and duplicate dnsmasq's logic
in interpreting them, before it could know whether or not dnsmasq
listens on 127.0.0.1. Furthermore the admin may not want 127.0.0.1
registered with resolvconf even if dnsmasq listens on it, or may want a
non-loopback address registered with resolvconf when dnsmasq doesn't
listen on any loopback address....
I conclude that we should only make the initscript as complex as
necessary, and not more so. I'll mark this as invalid until it's clear
that the change is really needed.
** Changed in: dnsmasq (Ubuntu)
Status: New => Invalid
--
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/1012102
Title:
Check all configuration files for except-interface lo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1012102/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
