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
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
|
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
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?
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.