Yeah, this looks like a bug. The systemd-resolved.postrm is copying
/run/systemd/resolve/resolv.conf to /etc/resolv.conf, rather then
copying /run/systemd/resolve/stub-resolv.conf (which is where
/etc/resolv.conf is symlinked to prior to removal).
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2056153
Title:
Removing the systemd-resolved package breaks DNSSEC validation
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Removing the systemd-resolved package breaks glibc DNSSEC validation,
because it removes an existing line from the new /etc/resolv.conf
file.
This line should be retained so that packages like Exim can continue
to use the AD bit after systemd-resolved is removed.
ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf
nameserver 127.0.0.53
options edns0 trust-ad
search vcn.oraclevcn.com
ubuntu@instance:~$ sudo apt remove systemd-resolved
ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf
nameserver 169.254.169.254
search vcn.oraclevcn.com
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056153/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
