If the "dnsmasq" package is not installed then purging the dnsmasq
package will remove /etc/init.d/dnsmasq and solve your problem.
Do not purge or remove the "dnsmasq-base" package. The dnsmasq-base
package includes the dnsmasq binary which is used by NetworkManager.
Of course, the question remai
I don't remember having installed or setup the standalone dnsmasq daemon
in the past. The dnsmasq package isn't installed (dnsmasq-base and
dnsmasq-utils are though), yet it does appear that /etc/init.d/dnsmasq
exists and does register 127.0.0.1 with resolvconf.
In /etc/default/dnsmasq it has ENAB
/run/resolvconf/interface/lo.dnsmasq arises from /etc/init.d/dnsmasq
registering the standalone dnsmasq's listen address 127.0.0.1 with
resolvconf. Normally the standalone dnsmasq listens at all addresses
including 127.0.0.1. Did you have the standalone dnsmasq running?
It is normal that "nameserv
Yes, it's in /run/resolvconf/interface/lo.dnsmasq
I deleted the file and restarted network-manager and resolv.conf is
generated correctly.
Weird that it completely ignored the other file in that directory,
/run/resolvconf/interface/NetworkManager, which had the correct
nameserver line but was nev
Can you find the "nameserver 127.0.0.1" line in one of the files in
/etc/resolvconf/resolv.conf.d/ or /run/resolvconf/interface ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315741
Title:
After u
