Public bug reported: Description: Ubuntu jaunty (development branch) Release: 9.04 avahi 0.6.23-2ubuntu3
Avahi causes local FQDN's ending with .local not resolvable. This is an old problem which has a few workarounds but has never been fixed to work out of the box. This problem will occur and be unsolvable for many (new) users trying to hook up there ubuntu (laptop) to an existing local (.local) domain. This problem can (easily) be solved by adding a bootup script to the Avahi/nss-mdns package. This method is even advised on the avahi wiki (http://www.avahi.org/wiki/AvahiAndUnicastDotLocal): <<++begin script++>> #!/bin/sh if host -t SOA local. > /dev/null 2> /dev/null ; then # Hoho! There is a domain .local in unicast DNS! Let's disable Avahi! if test -x /etc/init.d/avahi ; then /etc/init.d/avahi stop > /dev/null 2> /dev/null if test -x /usr/bin/logger ; then logger -p daemon.warning -t avahi <<EOF Avahi detected that your currently configured local DNS server serves a domain .local. This is inherently incompatible with Avahi and thus Avahi disabled itself. If you want to use Avahi in this network, please contact your administrator and convince him to use a different DNS domain, since .local should be used exclusively for Zeroconf technology. For more information, see http://avahi.org/wiki/AvahiAndUnicastDotLocal EOF fi fi fi <++end script++> Could be me but the script might be a little outdated (replace avahi with avahi-daemon). ** Affects: avahi (Ubuntu) Importance: Undecided Status: New -- Avahi is missing bootup script when DNS configuration changes https://bugs.launchpad.net/bugs/320164 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
