Hi all,
Thanks for the feedback. The point re: bringing up a second package is well-taken. I originally added that because the root cause for why mDNS support was disabled was to prefer Avahi, but I see how it can be confusing here. I also understand the confusion about mDNS, so I tried adding a line to illustrate the use cases where Debian admins may be affected. Hopefully it's helpful without being overly complex.
How does the following look:
For trixie, support for [mDNS](
https://en.wikipedia.org/wiki/Multicast_DNS) in systemd-resolved has been disabled by default. This has been done to prevent conflicts for users who have both systemd-resolved and avahi-daemon installed.
If you rely on systemd-resolved for mDNS resolution of *.local DNS names, or for answering mDNS queries from other hosts, you can mask the new drop-in config file so that mDNS support in systemd-resolved remains enabled. To do so, execute the following commands as root prior to upgrading systemd-resolved:
mkdir -p /etc/systemd/resolved.conf.d/
touch /etc/systemd/resolved.conf.d/00-disable-mdns.conf
Best,
Colin