> It's better to eliminate the behavioral conflict, if we can, than to formalize that conflict as a packaging dependency.
I was about to say this: But then the main problem which caused me to report this bug would remain: When I install the dnsmasq package, it wouldn't work. I'd configure my dnsmasq, then put 127.0.0.1 as the DNS server for my LTSP client sessions on the server, and another dnsmasq would answer which wouldn't contain my configuration, my A or MX records or whatever else I'd put in my configuration file. ...but then I thought of this, which if it worked, I wouldn't have problems: If nm + resolvconf managed to properly chain the 2 dnsmasq instances, so that the NM-spawned dnsmasq was contacted first in another address or port or IPv6 or whatever, and then the NM-spawned dnsmasq contacted my real dnsmasq at 127.0.0.1, since it's the DNS server I declared at my connection properties, then it would at least work as expected, with just a small additional overhead. I wouldn't mind about that. And it would work with any DNS server too, not with just dnsmasq. -- 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 running, yet network-manager doesn't Conflict with their packages Status in “djbdns” package in Ubuntu: New Status in “dnsmasq” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: Triaged 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
