Why systemd-resolved Breaks Avahi Print Discovery and How to Get Them Working Together
Joe B.
Reviewed for technical accuracy
Specialities: CUPS/IPP, Avahi & mDNS, systemd-resolved, cups-browsed, Ubuntu/Fedora/Arch
Fix Linux printer discovery — systemd-resolved vs Avahi, mDNS/DNS-SD, nss-mdns, CUPS & cups-browsed
Quick answer: the accepted fix
Accepted fix when systemd-resolved breaks mDNS printer discovery: run avahi-daemon for DNS-SD/mDNS with nss-mdns; set MulticastDNS=no in resolved (or avoid overlapping responders); allow UDP 5353; restart CUPS and optionally enable cups-browsed to auto-create IPP queues.
Why discovery breaks: DNS-SD with Avahi, .local resolution, and CUPS
CUPS discovers printers via DNS-SD/mDNS (Bonjour). On most Linux systems, Avahi advertises and discovers these services, while nss-mdns resolves .local hostnames. If systemd-resolved also tries to handle mDNS, the two stacks can conflict and IPP devices vanish from dialogs. Standardizing on Avahi for service discovery restores IPP/IPPS printers reliably.
How to verify the Linux print stack is healthy
Check avahi-browse -rt _ipp._tcp for advertised printers, confirm lpinfo -v lists IPP URIs, and print a CUPS test page. On servers, enable Browsing Yes or sharing in the CUPS web UI so clients see your queues via DNS-SD. For client autoconfig, enable cups-browsed to subscribe to mDNS and create local queues.
Avahi & systemd-resolved — quick checklist
Bring back network printer discovery in minutes.
Install nss-mdns → enable avahi-daemon → set MulticastDNS=no in systemd-resolved (or avoid overlap) → open UDP 5353 → restart CUPS → optionally enable cups-browsed for auto-queues → verify with avahi-browse and lpinfo.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your environment, please consult a verified expert on Whizz-Tech before making decisions.
Getting Started Is Easy
Ask for help, 24/7
Members enjoy round-the-clock access to experts in Linux printing, Avahi/mDNS, and CUPS configuration.
Expert will respond in minutes
We match you with an Expert who can fix DNS-SD/mDNS discovery, align Avahi and systemd-resolved, and restore IPP printing.
Save time & money
Avoid downtime and re-installs: a clean Avahi/CUPS setup brings back printers reliably.
FAQ
Why did printers disappear after a Linux update?
Updates may enable systemd-resolved mDNS or change nsswitch.conf, conflicting with Avahi. CUPS relies on DNS-SD via Avahi on most distros; when stacks overlap, discovery fails.
Do I need Avahi if systemd-resolved supports mDNS?
For CUPS printer discovery, keeping Avahi as the service discovery layer with nss-mdns is the most compatible route. Resolved can stay for standard DNS.
What firewall rule is required for printer discovery?
Allow UDP 5353 (mDNS) on the LAN interface so DNS-SD advertisements can be sent/received. Without it, IPP printers won’t appear.
Should I run cups-browsed?
cups-browsed subscribes to mDNS and can auto-create local queues for discovered printers — useful for fleets or multi-subnet environments.
| Symptom | Likely cause | Quick fix |
|---|---|---|
| No IPP printers appear | mDNS conflict: resolved vs Avahi | Let Avahi handle mDNS; set MulticastDNS=no in resolved; install nss-mdns |
| .local names don’t resolve | Missing nss-mdns or bad nsswitch.conf |
Add mdns to hosts line; restart Avahi |
| Printers visible via avahi-browse, not in CUPS | cups-browsed disabled | Enable cups-browsed; restart CUPS |
| Discovery works only off-VPN | mDNS blocked on VPN/multi-NIC | Allow UDP 5353 on LAN; limit mDNS to local interfaces |
Step-by-step (Linux desktop)
- Install nss-mdns; enable and start avahi-daemon.
- In
/etc/nsswitch.conf, ensuremdns/mdns4_minimal [NOTFOUND=return]precedesdnson the hosts line. - Set
MulticastDNS=noinsystemd-resolved(or avoid overlapping mDNS responders); restart it. - Open UDP 5353 on the LAN zone; restart CUPS and optionally enable cups-browsed.
Notes for mixed environments
- Apple devices use Bonjour (mDNS/DNS-SD); once Avahi handles mDNS, Linux will discover AirPrint printers reliably.
- For Windows clients, sharing via IPP on CUPS works well; avoid WSD on the Linux side for consistency.
Sources
- ArchWiki — CUPS (DNS-SD via Avahi)
- ArchWiki — Avahi (nss-mdns & configuration)
- Red Hat — Using cups-browsed (DNS-SD discovery)
Filed under: General Printer Problems
Related articles
- Canon EOS photo print soft — color space mismatch checks
- Pathology slide images print black — JPEG2000 decode fixes (SVS/WSI)
- ShareFile viewer breaks print scaling — direct PDF route
- Mesh Roaming Is Breaking Your Print Jobs — Why It Happens and How the Sticky Client Fix Solves It
- Square KDS kitchen print delay — UDP broadcast fix
- Blackboard LMS pages print double-margins — browser & print CSS fixes (Chrome/Edge/Firefox)
- PDF Form Fields Print Black Boxes — Full Fix Guide
- Dental panoramic slips print too dark — tone compression curve