[Bug 923685] Re: New resolver package overwrites manually created resolv.conf on server

[Steve Langasek]

On Sat, Feb 11, 2012 at 08:16:57PM -0000, Thomas Hood wrote:
> Here's the next iteration of the proposal.

> 1) /etc/resolv.conf contains no nameserver information => exit
> 2) "Generated by NetworkManager" in /etc/resolv.conf => exit
> 3) /etc/network/interfaces contains "mapping" or "source" lines => append

A 'mapping' stanza should have no effect at all on whether we append.

If a 'source' stanza exists at all, it most likely points to other interface
definitions that *do* provide resolver info, so why would we want to append
in that case except as a last resort?  I.e., I think this also collapses
into the fallback case 6).

> 4) /etc/network/interfaces contains a logical interface definition with
> name N and configuration method name "dhcp" and the file also contains an
> "auto N" line => exit
> 5) /etc/network/interfaces contains a logical interface definition with
> name N and a "dns-nameservers" option and the file also contains an "auto
> N" line => exit

The plan I discussed with Stéphane explicitly does *not* require the auto
line for either of these.  The reasoning is that there is already an
interface definition which we know will overwrite the resolver info in some
cases, so /etc/resolv.conf is *not* static.  If the admin assumed it was
static, then they've made a judgement error; resolvconf is merely exposing
this error, not causing a bug in its own right.

> 6) Append

So I think that, modulo the dropping of 3) ifquery, the earlier proposal
from Stéphane is still what we want to go with.

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