The network-manager package still ships /etc/dnsmasq.d/network-manager with "bind-interfaces" in it and that breaks the TFTP server of dnsmasq and sometimes even the DNS server of dnsmasq.
"bind-dynamic" is a little better, but too unreliable to be used in production. So this bug is still not resolved, after 150 messages it was just made a little worse. One workaround is to undo the "solution" offered in this bug report: 1) In /etc/NetworkManager/NetworkManager.conf, comment out: # dns=dnsmasq 2) And in /etc/dnsmasq.d/network-manager, comment out: #bind-interfaces A better solution would be for Mathieu to create a separate package for the nm-spawned dnsmasq, one that would conflict with the real dnsmasq server so that it would be automatically uninstalled when the sysadmin would install the real dnsmasq. I can send a patch for that if it will be accepted. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
