[Bug 1315741] Re: The dnsmasq initscript fails to disable itself when the dnsmasq package is removed

[Thomas Hood]

> the script fails to look at the return value

I was wrong; the script does look at the return value.

** Package changed: resolvconf (Ubuntu) => dnsmasq (Ubuntu)

** Also affects: dnsmasq
   Importance: Undecided
       Status: New

** No longer affects: dnsmasq

** Also affects: dnsmasq (Debian)
   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:
  The dnsmasq initscript fails to disable itself when the dnsmasq
  package is removed

Status in “dnsmasq” package in Ubuntu:
  Confirmed
Status in “dnsmasq” package in Debian:
  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/dnsmasq/+bug/1315741/+subscriptions