Comment 40 for bug 366967

> my /etc/resolv.conf file got blown away
> [...]
> But guess what, no more clean reboots. Each reboot requires an ifdown/ifup ritual.

As Steve mentioned, the resolvconf package was not an official part of Ubuntu prior to 12.04. In earlier releases it was available from the Universe repository but was broken such that after boot it was necessary to ifdown and ifup, just as you say.

To fix this now you can choose either to remove the resolvconf package or update to the version (1.63ubuntu8) from the Precise repository.

Resolvconf has been available in Debian for about eight years now and has thousands of users. Once in a while the Debian maintainers receive complaints like yours, but these unhappy experiences have always proved to have been a result of misunderstanding about how resolvconf is supposed to work. The resolvconf package collects nameserver information and keeps a file, /run/resolvconf/resolv.conf, up to date; /etc/resolv.conf is linked to /run/resolvconf/resolv.conf. If you don't want this feature then, in a terminal, as root, do "dpkg --purge resolvconf" and edit /etc/resolv.conf.

(It may have occurred in the past that another package pulled in resolvconf via a Recommends dependency. We apologize for that, combined with the fact that the Ubuntu resolvconf package was not properly maintained.)

I think it would be better, however, if you learned a bit more about resolvconf --- especially since Ubuntu 12.04's ubuntu-minimal will depend on it: please read /usr/share/doc/resolvconf/README.gz.