FS#59748 - [nss-mdns] nss-mdns-0.14.1-1 no longer works

Attached to Project: Arch Linux
Opened by Yichao Zhou (zhou13) - Wednesday, 22 August 2018, 07:07 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 25 August 2018, 14:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

nss-mdns-0.14.1-1 no longer works for mdns resolve.


Steps to reproduce:
1. edit /etc/nsswitch.conf so that the hosts line looks like: hosts: files mymachines myhostname mdns_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns

2. ping XXXXX.local

3. it returns ping: XXXXX.local: Name or service not known

downgrade it to 0.10-7 works for me.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 25 August 2018, 14:59 GMT
Reason for closing:  Not a bug
Comment by Antonio Rojas (arojas) - Wednesday, 22 August 2018, 07:21 GMT
Works fine here. Have you restarted the avahi-daemon service after updating? Anything special about your setup?
Comment by Yichao Zhou (zhou13) - Wednesday, 22 August 2018, 22:12 GMT
Yes. I tried to restart avahi-daemon. In addition, "avahi-resolve --n XXX.local" shows the correct IP address for me. I am not aware of any special configuration about mDNS.
Comment by Yichao Zhou (zhou13) - Wednesday, 22 August 2018, 22:15 GMT
I also tried to restart my computer. nss-mdns-0.14.1-1 still does not work.
Comment by Yichao Zhou (zhou13) - Friday, 24 August 2018, 06:12 GMT
It seems that the bug was introduced by https://bugzilla.redhat.com/show_bug.cgi?id=1565359. It says

If, during a request, the system-configured unicast DNS (specified in /etc/resolv.conf) reports an SOA record for the top-level local name, the request is rejected. Example: host -t SOA local returns something other than Host local not found: 3(NXDOMAIN). This is the unicast SOA heuristic.

This heuristic can be disabled by echo .local | sudo tee /etc/mdns.allow .

I guess this is caused by the AT&T's DNS server. If I switched to 1.1.1.1, everything works fine. Maybe nss-mdns can ship a default mdns.allow?
Comment by Yichao Zhou (zhou13) - Friday, 24 August 2018, 06:54 GMT
Also we need to replace mdns_minimal with mdns.
Comment by nl6720 (nl6720) - Friday, 24 August 2018, 08:03 GMT
Using "mdns" instead of "mdns_minimal" will significantly increase reverse lookup time ( https://github.com/lathiat/nss-mdns/issues/46#issuecomment-381936000 ), so recommending "mdns" as the default is not desirable.

You have already found the solution - use a non-broken DNS server or follow the instructions in https://github.com/lathiat/nss-mdns/blob/master/README.md#etcmdnsallow . If you want you can add this information to the Avahi page on ArchWiki.

Loading...