Comment 12 for bug 1672099
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Where does the dnsmasq package come from that is listening on 127.0.0.1? dnsmasq should normally not be listening on that address if it was spawned by NetworkManager.
Do you have the 'dnsmasq' package installed instead of dnsmasq-base? dnsmasq-base can be used in a variety of scenarios as a local nameserver and/or for lxc/libvirt and other uses.
dnsmasq ships a service file which by default might conflict with resolved. If you need dnsmasq to run a nameserver on that system, you would have to make sure the configuration of the whole system is such that both would not conflict.
This can be achieved in two different ways:
- Setting DNS= in resolved if you want to use resolved as an authoritative nameserver to provide dnsmasq with the information it needs (but not circle back to dnsmasq).
- Setting 'no-resolv' and possibly other settings for the dnsmasq instance, such that it doesn't go ask systemd-resolved for nameservers, and that it does not update resolv.conf if it should not.