Public bug reported:
systemd-resolved is a standard component of Ubuntu in 20.04. We should
not have packages in the archive - some of which may be installed on
users' systems as a result of upgrading from previous releases - that
cause the handling of DNS resolution to diverge from the default.
This means that:
- the dhclient hook that picks up DNS settings should only feed settings
directly to resolved, and not via resolvconf.
- resolvconf must not change the target of /etc/resolv.conf and on upgrade must
correct it.
- resolvconf must feed its settings reliably into resolved rather than pulling
resolved settings into resolvconf.
- systemd should not ship a dhclient hook at all because dhclient is not used
by any systems that use netplan for network management, it is only needed for
compatibility on upgrade with ifupdown; so move the hook to the ifupdown
package.
** Affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
** Affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
** Also 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/1874337
Title:
resolvconf should never touch /etc/resolv.conf in Ubuntu; all DNS
configuration from resolvconf, ifupdown, and dhclient should always be
fed directly to systemd-resolved.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1874337/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
