Am 05.08.24 um 11:45 schrieb Luca Boccassi:
On Mon, 5 Aug 2024 at 10:31, Laurent Bigonville <bi...@debian.org> wrote:On Mon, 05 Aug 2024 00:15:00 +0100 Luca Boccassi <bl...@debian.org> wrote: > I'm not sure what could be done here, and I don't think anything should > even if it could. Either don't install/enable both at the same time, or > disable mDNS in resolved (it's optional). The avahi-daemon is pulled by some packages and disabling it completely will break stuff. It seems that Fedora has gone the "disable mDNS support by default in systemd-resolved" route: https://src.fedoraproject.org/rpms/systemd/blob/rawhide/f/systemd.spec#_793 An other option could be to let avahi-daemon puts a snippet to disable systemd-resolved mDNS support in /etc/systemd/resolved.conf.d/ So what's your preferred way here?I do not want to disable it globally as it's possible to just disable avahi, but if Michael wants to ship a drop-in for resolved in avahi that's fine by me, as the drop-in can be masked locally too
I would prefer the solution Fedora has chosen, i.e. build systemdwith -Ddefault-mdns=no. This will provide a more predictable behaviour for systemd-resolved and is imho a cleaner solution. Users that want the mdns functionality can easily opt-in via a config snippet.
Regards, Michael
OpenPGP_signature.asc
Description: OpenPGP digital signature