[Bug 923685] Re: Installing resolvconf causes loss of manually entered nameserver information in resolv.conf

[Steve Langasek]

>> It looks as if you can omit step 3 in your algorithm.
> indeed, 3) won't match either 4) or 5) and so will be caught by 6) giving the same result

Except in the case that there are inet dhcp entries in /e/n/i that are
*not* marked auto.  Thinking about whether this should actually be
handled differently.

** Changed in: resolvconf (Ubuntu Precise)
     Assignee: Canonical Foundations Team (canonical-foundations) => Steve Langasek (vorlon)

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

Title:
  Installing resolvconf causes loss of manually entered nameserver
  information in resolv.conf

Status in “resolvconf” package in Ubuntu:
  In Progress
Status in “resolvconf” source package in Precise:
  In Progress

Bug description:
  Release: Precise
  Architecture: amd64

  This is something I noticed when recently doing updates on my Precise test server. Before I had set up a /etc/resolv.conf (cannot remember when but maybe the installer did) so it would point to the correct nameserver and search list(s). And that was left alone all the time (on a server installation). But the  recent update to resolvconf changed that and the dns configuration was dropped (because the static ip setup in /etc/network/interfaces did not have any dns-* keywords).
  Now this is simple to fix by adding dns-nameserver and dns-search to the interfaces file, but (assuming many servers have a static ip setup and not dhcp) could cause a lot of fallout for upgrades.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/923685/+subscriptions