With Avahi bug #311, I understand it was agreed the bug was on<br>Lennart to fix.<br><br>Still, I would just like to reiterate that in 2013 on some misconfigured<br>public hotspots the avahi-daemon-check-dns.sh indeed doesn't stop<br>

the daemon, which makes the hotel hotspot unavailable to the unaware<br>travelling novice.<br><br>For the particular server I have in mind, no DNS records exist for domain<br>'local':<br>$ nslookup<br>> server<br>

Default server: 10.5.50.1<br>Address: 10.5.50.1#53<br>><br>> hotspot.plaza.local<br>Server:        10.5.50.1<br>Address:    10.5.50.1#53<br><br>Non-authoritative answer:<br>Name:    hotspot.plaza.local<br>Address: 10.5.50.1<br>

><br>> plaza.local<br>Server:        10.5.50.1<br>Address:    10.5.50.1#53<br><br>Non-authoritative answer:<br>Name:    plaza.local<br>Address: 192.168.120.97<br>Name:    plaza.local<br>Address: 192.168.120.99<br>><br>

> local<br>Server:        10.5.50.1<br>Address:    10.5.50.1#53<br><br>** server can't find local: SERVFAIL<br>> ><br><br>And /etc/resolv.conf holds:<br>$ cat /etc/resolv.conf<br>domain hotspot.plaza<br>search hotspot.plaza<br>

<br>OS X indeed has no trouble connecting.<br>