Public bug reported:
Moving off of resolvconf and to systemd-resolved requires that
resolv.conf is properly handled both in the case of new installs (done
as per 234-2ubuntu9 at least), but also in the case of upgrades from
previous releases or previous versions of systemd.
There are various use cases to take into account:
1) upgrades where resolv.conf is more or less default and dynamic, uses
DHCP via ifupdown (servers), or 127.0.1.1/DHCP settings from
NetworkManager (desktops), etc.
2) upgrades from manual resolv.conf settings (the user has written their
own, it's static)
3) upgrades from manual resolv.conf managed via resolvconf.
3) No resolv.conf?
Lack of resolv.conf is simple, writing one is always sane.
Upgrades from dynamic files is also straightforward, copying it to
/run/systemd/resolve/resolv.conf will keep the current state;
/etc/resolv.conf will be symlinked to that.
In the case of a manually-configured resolv.conf; whether it comes from
resolvconf or is manually configured is non-trivial if we want to
maintain the current DNS configuration and also remove resolvconf. The
removal of resolvconf can be forced, but what do we do about the
existing /etc/resolv.conf file, knowing that /run is a tmpfs?
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713578
Title:
Migrate /etc/resolv.conf from resolvconf to systemd-resolved
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713578/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
