I would say either way is fine, reading a configuration file or directly
communicating with resolvconf.
Directly communicating with resolvconf is the best solution.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
htt
** Description changed:
- The system dnsmasq is preventing nameservice from working with
- NetworkManager. By setting /etc/deafault/dnsmasq ENABLED=1 to ENABLED=0,
- nameservice started working again.
+ The standalone Dnsmasq (from the dnsmasq package) is preventing the
+ NetworkManager-controlled
Currently it's the initscript that talks to resolvconf. If we want the
initscript to implement the behavior requested here (i.e., "register
127.0.0.1 with resolvconf if and only if dnsmasq is listening on lo")
then the initscript will have to understand dnsmasq's configuration
files. That's asking
This remains a bug, but fixing bug 1044388 is going to make this a much
more rare occurence.
Unassigning for now, the bug needs to be filed upstream and fixed by the
upstream maintainer.
** Changed in: dnsmasq (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
--
You r
I wrote in comment #5:
> If so, then that's a second bug for which another report can be opened.
I opened bug #1044388 about this.
--
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/10422
** Summary changed:
- network-manager dnsmasq configuration snippet causes standalone dnsmasq not
to listen on 127.0.0.1, breaking name service when dnsmasq is installed
+ dnsmasq should not register 127.0.0.1 with resolvconf if it's not listening
on lo
--
You received this bug notification be
