Ubuntu
resolvconf package

  1. Bug #923685
  2. Comment #16

Comment 16 for bug 923685

Revision history for this message
Thomas Hood (jdthood) wrote : Re: New resolver package overwrites manually created resolv.conf on server

Steve wrote:
> Ubuntu policy prohibits debconf prompting [...]

1. OK, no prompting. :)

If we don't debconf-prompt then what's the best way of letting the admin know that she should edit /e/n/i?

> (AFAICS, the proposal above would result in prompts
> for any desktop system that is using NM exclusively
> for network configuration - which would mean there
> are no auto interfaces in /e/n/i.)

2. You are right, I forgot to mention NM in the conditions.

Proposal version 2:

If there is nameserver information in the original /etc/resolv.conf which wasn't written by NetworkManager and there is nothing set up to supply dynamic nameserver information then adjust link-tail-to-original's default value to "true". By "nothing is set up to supply dynamic nameserver information" we mean: NetworkManager is not active and there is no physical interface marked "auto" in /e/n/i for which there is a logical interface definition in /e/n/i that is either "dhcp"-methodic a "static"-methodic with "dns-" lines.

My own familiarity with networking setups is not exceptionally broad, so it would be good if someone who does have broad familiarity would look at this proposal and think about consequences for, e.g., servers with multiple network interfaces, laptops with VPN interfaces, etc.
--
Thomas