[Bug 1315741] Re: After upgrading from 12.04 to 14.04, network manager puts 127.0.0.1 instead of 127.0.1.1 in resolv.conf
Thomas Hood
1315741 at bugs.launchpad.net
Sat May 3 20:57:33 UTC 2014
/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 "nameserver 127.0.1.1" was in
/run/resolvconf/interface/NetworkManager but not included in
resolv.conf. Resolvconf normally includes at most one loopback address
in resolv.conf.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1315741
Title:
After upgrading from 12.04 to 14.04, network manager puts 127.0.0.1
instead of 127.0.1.1 in resolv.conf
Status in “resolvconf” package in Ubuntu:
New
Bug description:
I upgraded from 12.04 to 14.04 and found that I had no DNS. After a
little searching I noticed that dnsmasq, as started by Network
Manager, was listening on 127.0.1.1, yet /etc/resolv.conf was being
auto-populated with 127.0.0.1, so DNS lookups were failing.
Manually adding 127.0.1.1 to /etc/resolv.conf lets DNS work until the
network state changes, then it gets overwritten again with 127.0.0.1.
I've worked around the issue by adding "nameserver 127.0.1.1" to
/etc/resolvconf/resolv.conf.d/head and restarting network-manager.
Something left over from 12.04 is apparently still causing 127.0.0.1
to be written instead of 127.0.1.1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1315741/+subscriptions
More information about the foundations-bugs
mailing list