avahi causes all .local names to fail to resolve

[David Given]

Avahi apparently overrides the .local domain to present discovered services to the user. Unfortunately, my intranet uses the .local suffix; the result is that 'chur' will resolve, but 'chur.local' will not, and doesn't even attempt to contact the DNS server.

While I am aware (now) that I can't use avahi if my local domain is called .local, it did take me about an hour of confused debugging to figure out what was going on; this absolutely needs to be conveyed better to the user.

DHCP is producing a /etc/resolv.conf file that looks like this:

# Generated by NetworkManager
domain local
search local
nameserver 10.0.0.1

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: avahi-daemon 0.6.27-2ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Oct 10 22:41:27 2010
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: avahi