From 802dc1c4c8a996a35caa85ee18ac568625e746ef Mon Sep 17 00:00:00 2001 From: Aminda Suomalainen Date: Sat, 7 Mar 2026 10:05:03 +0200 Subject: [PATCH] systemd-resolved: clarify no Service Discovery --- .../resolved.conf.d/91-replace-avahi.conf.breaks-cups | 5 ----- etc/systemd/resolved.conf.d/README.md | 2 ++ 2 files changed, 2 insertions(+), 5 deletions(-) delete mode 100644 etc/systemd/resolved.conf.d/91-replace-avahi.conf.breaks-cups diff --git a/etc/systemd/resolved.conf.d/91-replace-avahi.conf.breaks-cups b/etc/systemd/resolved.conf.d/91-replace-avahi.conf.breaks-cups deleted file mode 100644 index 23dd4aa7..00000000 --- a/etc/systemd/resolved.conf.d/91-replace-avahi.conf.breaks-cups +++ /dev/null @@ -1,5 +0,0 @@ -# Enable resolver and responder, practically replacing avahi-daemon -[Resolve] -LLMNR=true -MulticastDNS=true -# vim: filetype=systemd diff --git a/etc/systemd/resolved.conf.d/README.md b/etc/systemd/resolved.conf.d/README.md index 4dd42731..644e2fcf 100644 --- a/etc/systemd/resolved.conf.d/README.md +++ b/etc/systemd/resolved.conf.d/README.md @@ -53,6 +53,8 @@ offer. will be used when it won't work anymore and then the next is used as long as it works and then it's back to the beginning. - https://github.com/systemd/systemd/issues/16322#issuecomment-724143641 +- While systemd-resolved can do mDNS (multicast DNS), it cannot do DNS-SD + (service discovery). Thus no local CUPS printing. Other links I have found important and my files are based on: