[Bug 1315741] [NEW] After upgrading from 12.04 to 14.04, network manager puts 127.0.0.1 instead of 127.0.1.1 in resolv.conf

[Josh Hill]

Public bug reported:

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.

** Affects: resolvconf (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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