Comment 3 for bug 111834

The idea of this patch is to DISABLE avahi when it won't work properly. This patch is more likely to disable avahi, so since it seems that you want avahi to be running, my guess is that this is not your problem.

Basically, avahi should be disabled if you need to be able to look up names that end in .local using DNS. You probably know whether or not that is the case.

To determine if this patch will do anything on your network, first do

host -t soa local.

If it returns with

Host local not found: 3(NXDOMAIN)

then this patch will not help you, and avahi should not have any problems related to a unicast .local domain. If it returns something else that looks like

local has SOA record blah.blah. blah.blah. 2 3600 600 604800 86400

Then you have a unicast local. domain. If avahi is not being disabled in this case, you could apply the patch with something like

patch -b -i patchfile /etc/network/if-up.d/avahi-daemon

where patchfile is the name that you saved the patch as. Make sure you save a copy of /etc/network/if-up.d/avahi-daemon before doing this, this patch has not received extensive testing!