This bug is causing a lot of problems. As the avahi-daemon is enabled
by default, you need a great deal of knowledge to know what is going
on here. For instance, our Microsoft network in the office uses the
popular .local pseudo domain.
When connected to the VPN:
ping server - Works fine
ping server.ourdomain.local - Times out.
When in the office, and on the local LAN, I can't resolve .local
hostnames at all when using actual services (i.e. SSH, ping etc).
To compound things, lookups using dig, host or nslookup commands all
work fine. Thereby confusing me even further.
If I do:
sudo /etc/init.d/avahi-daemon stop
Magically, FQDN lookups work again. It took me a long time to find
this out :)
FQDN lookups on .local domains are essential to anyone who uses a
Microsoft network. And lots of people don't have reverse lookups
configured for their local IP addresses - this is a very common
problem. I know, we probably should have, but if everything works
properly, why change it?
For now, I'll just disable the daemon, but it would be nice for other
people not to have to fall foul of this, since it's such basic
functionality.
thanks,
Chris
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
