getent does not resolve host in .local while avahi does

Bug #1945097 reported by MagnusPI
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glibc (Ubuntu)
New
Undecided
Unassigned

Bug Description

To reproduce:
1)Set up a shared printer.
2) On a computer in the same local network the printer is seen by cups as a dnssd printer.
3) After setting up the printer as a dnssd printer cups cannot print since it cannot locate the printer.

avahi -a -r and avahi-resolve-host-name are able to resolve the host with the printer.
getent cannot resolve it and cups fails.

As suggested in
https://ask.fedoraproject.org/t/avahi-isnt-being-used-to-resolve-local-domain-names/4911/8
the issue is related to mdns4_minimal in /etc/nsswitch.conf and the absence of /etc/mdns.allow

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libc-bin 2.31-0ubuntu9.2
ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 26 13:32:43 2021
InstallationDate: Installed on 2020-10-06 (354 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: glibc
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
MagnusPI (ipesando) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.