resolving .local addresses

[NoOp]

On 06/28/2009 08:54 AM, NoOp wrote:
...
> Perhaps:
> https://bugs.launchpad.net/ubuntu/+source/avahi
>  https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/80900
> [problems resolving fully qualified domain names in environments where
> .local is used as a TLD]
> are of interest.
> 
> Also:
> http://avahi.org/
> http://www.zeroconf.org/
> https://help.ubuntu.com/community/HowToZeroconf
> http://manpages.ubuntu.com/manpages/jaunty/man8/avahi-daemon.8.html
> <http://blog.ibeentoubuntu.com/2009/04/avahi-zeroconf-problem-with-ubuntu-904.html>

Sorry I forgot to add these:
https://wiki.ubuntu.com/JauntyJackalope/ReleaseNotes
<quote>
Avahi will not start if a .local domain is present

The avahi-daemon package, which implements the mDNS "zeroconf" standard,
includes a check to avoid running when a conflicting .local DNS domain
is present. It is reported that some ISPs advertise such a .local domain
on their networks, which will leave Ubuntu 9.04 hosts unable to see
names advertised on the local network (327362).

To force the use of mDNS on a network configured this way, users can run
the commands:

sudo sed -i -e'/AVAHI_DAEMON_DETECT_LOCAL/s/1/0/' /etc/default/avahi-daemon
sudo service avahi-daemon start
</quote>

https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/327362
<Some ISPs have .local domain which disables avahi-daemon>