network-manager should not turn on dnsmasq's "except-interface=lo" option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
High
|
Mathieu Trudel-Lapierre |
Bug Description
As of n-m 0.9.6.0-0ubuntu4 NM listens on 127.0.1.1 rather than 127.0.0.1. So there is no longer any need to prevent standalone dnsmasq from binding lo's address, 127.0.0.1. So the line
except-
in /etc/dnsmasq.
Previous discussion of these issues was in bug #959037.
I append the relevant changelog entries.
network-manager (0.9.6.0-0ubuntu4) quantal; urgency=low
* debian/
dnsmasq (and bind) plugins should listen on for DNS resolution to 127.0.1.1,
as opposed to 127.0.0.1 to avoid conflicts with other instances that might
need to run on the system with that address.
[...]
network-manager (0.9.6.
[...]
* debian/
install a config file to /etc/dnsmasq.d to avoid system-wide instances of
dnsmasq to bind to 0.0.0.0 and the loopback interface, so that the NM-
spawned instance can claim an IP on lo and provide local resolution.
(LP: #959037)
Correct, that probably needs to go now.