You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation at http://0pointer.de/lennart/projects/nss-mdns/ says that by default (without /etc/mdns.allow present) nss-mdns behaves as though this file were there with the content:
.local.
.local
However this piece of documentation is not current. The dated page above puzzled me, and I believe the lack of updated information was the issue here, even though the topic-starter eventually blamed it on his router. But the behavior described is exactly what I've been getting until I created /etc/mdns.allow with its content.
So I believe a man page is needed:
Even where readme.md is present, many will habitually use "man foo".
In Arch and its derivatives there are no docs apart from man pages.
It had me scratching my head a lot of time before I realized why .local names were not being resolved :)
The text was updated successfully, but these errors were encountered:
I'm not a project maintainer, just another person trying to troubleshoot all this too.
I wonder if this is caused by using the minimal versions of mdns in /etc/nsswitch.conf? the minimal versions apparently won't read /etc/mdns.allow under any circumstances.
I was seeing 10-second name resolution delays with these:
ping prusa.local
getent hosts prusa.local --service="mdns_minimal"
but this would return almost immediately:
avahi-resolve prusa.local
I fixed it for my purposes by changing mdns4_minimal to mdns4 in /etc/nsswitch.conf and creating /etc/mdns.allow with these contents:
.local.
.local
and now getent hosts prusa.local --service="mdns" returns almost immediately, and ping works right away.
The documentation at http://0pointer.de/lennart/projects/nss-mdns/ says that by default (without
/etc/mdns.allow
present) nss-mdns behaves as though this file were there with the content:However this piece of documentation is not current. The dated page above puzzled me, and I believe the lack of updated information was the issue here, even though the topic-starter eventually blamed it on his router. But the behavior described is exactly what I've been getting until I created
/etc/mdns.allow
with its content.So I believe a man page is needed:
It had me scratching my head a lot of time before I realized why .local names were not being resolved :)
The text was updated successfully, but these errors were encountered: