I was re-visiting this recently, I'm fairly sure we can get rid of this requirement to stop avahi with a .local by reconfiguring nsswitch.conf to remove the [NOTFOUND=RETURN].
Do you know where the initial discussion determining why to do this was had? My general understanding is that because of the [NOTFOUND=RETURN] in nsswitch.conf, if avahi is started then .local domains wont resolve as mdns returns NOTFOUND for any .local then causing the lookup to short circuit and return failed. If we remove this flag, it should fall through to DNS and work as expected, though possibly with an increased timeout. Generally mDNS only has single depth hostnames that you lookup via regular dns, e.g. host1.local -- sub.host1.local is generally not allowed by the spec for normal hostnames. In contrast, most .local domains are active directory/windows or other domains where they usually have 3 levels, e.g. host.network.local -- if the timeout is an issue we could very likely fall through on multi label hosts if it's not in the cache. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1441008 Title: under systemd avahi-daemon doesn't stay disabled when .local is detected Status in avahi package in Ubuntu: Triaged Bug description: When avahi daemon detects .local unicast domain, the daemon is disabled. When a user tries to resolve a domain name through nss, the daemon starts up. The root cause is most likely in systemd that starts the daemon when an application tries to access the socket through the systemd managed socket file. This behavior wasn't observed in 14.10 or earlier releases, thus the assumption towards systemd socket activation. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: avahi-daemon 0.6.31-4ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 7 09:51:43 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-16 (506 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: avahi UpgradeStatus: Upgraded to vivid on 2015-03-18 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1441008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
