[Resolvconf-devel] Bug#628524: Re #628524: What to do?

Thomas Hood jdthood at gmail.com
Tue May 31 07:27:55 UTC 2011

So one solution is for all suppliers of nameserver information
to include resolvconf packaging-event hook scripts.  But that
is what we can call an, ahem, long-term solution.

In the meantime, how can we address the problem?

The crux of the problem is
1. resolvconf (normally) omits the external nameserver address from
resolv.conf when dnsmasq or another caching nameserver is installed;
2. resolvconf postrm leaves the contents of resolv.conf unchanged on removal.

Though neither behavior is cast in stone, both (1) and (2) are done
for good reasons.  I am reluctant to change either behavior and
I am also reluctant to do something ugly such as appending
/var/run/dnsmasq/resolv.conf to /etc/resolv.conf on remove.

If anyone has any other ideas, let's hear them.

One quick win (done for 1.55) is to print a "Reboot recommended"
message in the postrm.  We should turn this into a debconf note
so that it can be translated.

In the absence of new ideas I will just do this.

More information about the Resolvconf-devel mailing list