Add upstream suggested script to handle DNS .local domains
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
avahi (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
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://
<<++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
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://
EOF
fi
fi
fi
<++end script++>
Could be me but the script might be a little outdated (replace avahi with avahi-daemon).
Changed in avahi (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Triaged |
summary: |
- Avahi is missing bootup script when DNS configuration changes + Add upstream suggested script to handle DNS .local domains |