Package: cloud.debian.org Severity: important X-Debbugs-Cc: flavi...@magnux.com
Hello, Bookworm's release notes clearly states that "systemd-resolved was not, and still is not, the default DNS resolver in Debian" (https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#systemd-resolved) However apparently it is the default on the Debian provided AWS AMIs -- at least that's what I got out-of-box on a few instances I installed recently from the images in https://wiki.debian.org/Cloud/AmazonEC2Image/Bookworm for the us-east-2 and ca-west-1 regions. Goals here is not to discuss systemd idiosyncrasies, but I've only got headaches with systemd-resolved/-networkd to the point it's being easier to install Bullseye and upgrade (no extra systemd-nonsensed then, everything works). So I just want to clarify what's the current status quo regarding systemd-resolved/-networkd in cloud images so I can file bug reports properly. p.s.: same for polkitd -- not sure if we need a daemon "intended to be used by privileged programs offering service to unprivileged programs often through some form of inter-process communication mechanism" installed NOT TO SAY RUNNING on a purposedly minimal network server that virtually can only be acessed via ssh. I'm happy to file a bug report/wishlist item if necessary. Thank you, FVS