> * Change NM such that it causes its slave dnsmasq to listen on ::1 instead of 127.0.0.1
Personally, when I install dnsmasq, I *don't want* to use the NM-spawned dnsmasq, because it disables caching etc etc. So it wouldn't matter if it listened on another address, on a socket or wherever else; I wouldn't want it as my default resolver. I still think that the best idea is to make the local resolver a separate package that conflicts with all DNS servers, so that it's automatically uninstalled when one of them gets installed, until the problem is solved within libc. There are a lot of methods for interprocess communication, I'm sure some of them can solve the problem properly. That way all people would benefit, now the solution is only for those using Ubuntu+Network manager+resolvconf. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
