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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/959037 Title: NM-controlled dnsmasq prevents other DNS servers from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
