Mathieu: True, if dnsmasq is configured not to listen on lo (using "except-interface=lo") then it shouldn't write lo.dnsmasq. That's one bug.
But do you agree that "except-interface=lo" should no longer be included in /etc/dnsmasq.d/network-manager, since network-manager now listens on 127.0.1.1 and there is no need to prevent standalone dnsmasq from binding lo's address, 127.0.0.1? If so, then that's a second bug for which another report can be opened. -- 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/1042275 Title: network-manager dnsmasq configuration snippet causes standalone dnsmasq not to listen on 127.0.0.1, breaking name service when dnsmasq is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1042275/+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
