Ubuntu
resolvconf package

  1. Bug #923685
  2. Comment #5

Comment 5 for bug 923685

Revision history for this message
Stéphane Graber (stgraber) wrote : Re: New resolver package overwrites manually created resolv.conf on server

Right, so after talking with Stefan on IRC, the exact failing case is:
1) Installed system through debian-installer using DHCP configuration (choosing static there would have added the dns- fields)
2) Post-install, turned the system into static network configuration
3) Upgraded from Oneiric to Precise which added resolvconf

I'm guessing this might be a pretty likely scenario for servers indeed and we should be doing something about it.
Now I'm not sure whether we want to try and add the existing DNS servers (link-tail-to-original) or if we should instead show a debconf message telling the user about the change in the way we do DNS resolving and asking them to move /etc/resolvconf/resolv.conf.d/original to /etc/network/interfaces.

An option would be to use link-tail-to-original but only if we detect that we have interfaces in /etc/network/interfaces that are marked as auto but don't have dns- fields (easy to check with ifquery) and that we don't have Network Manager on the system.

I'd be against a link-tail-to-original by default as it'd mostly be confusing on systems where the DNS configuration is dynamic,