The fix for this issue caused another regression, dnsmasq now doesn't
function correctly as a tftp server either.
I just tried Trusty (dnsmasq 2.68-1), and network manager ships
/etc/dnsmasq.d/network-manager with:
bind-interfaces
So now dnsmasq only binds 127.0.0.1 for its tftp service:
udp 0 0 127.0.0.1:69 0.0.0.0:*
954/dnsmasq
udp6 0 0 ::1:69 :::*
954/dnsmasq
...and of course that breaks everything. Removing that file makes tftp
work again.
Mathieu, could you please package the modifications to
/etc/NetworkManager/NetworkManager.conf and to /etc/dnsmasq.d/network-manager
as a separate, network-manager-local-resolver.deb package, maybe even produced
by the network manager source code, and Recommented: it from network-manager,
...so that people that want to use dnsmasq as a real server can just
blacklist it without suffering on each new Ubuntu installation?
E.g. for the 500+ schools we maintain here, we could then just Conflict:
network-manager-local-resolver from our main package and forget the
whole thing...
Thanks,
Alkis
** Changed in: network-manager (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/959037
Title:
NM-controlled dnsmasq prevents other DNS servers from starting
Status in “djbdns” package in Ubuntu:
Confirmed
Status in “dnsmasq” package in Ubuntu:
Fix Released
Status in “network-manager” package in Ubuntu:
Confirmed
Status in “pdns-recursor” package in Ubuntu:
Invalid
Status in “pdnsd” package in Ubuntu:
Invalid
Status in “djbdns” source package in Precise:
Confirmed
Status in “dnsmasq” source package in Precise:
Triaged
Status in “network-manager” source package in Precise:
Triaged
Status in “pdns-recursor” source package in Precise:
Invalid
Status in “pdnsd” source package in Precise:
Invalid
Bug description:
As described in
https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-dns-
resolving, network manager now starts a dnsmasq instance for local DNS
resolving.
That breaks the default bind9 and dnsmasq installations, for people that
actually want to install a DNS server.
Having to manually comment out "#dns=dnsmasq" in
/etc/NetworkManager/NetworkManager.conf doesn't sound good, and if it stays
that way, it should be moved to the bind9 and dnsmasq postinst scripts.
Please make network-manager smarter so that it checks if bind9 or
dnsmasq are installed, so that it doesn't start the local resolver in
that case.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
