[avahi] Unexpected resolution failures

[Ludovic Courtès]

Hi,

At my office, I often notice that, after `avahi-daemon' has been running
for some time, several services suddenly become "unresolvable".
Restarting the daemon magically makes them resolvable again.
Concretely, here is what I observe:

  $ avahi-browse -rk _daap._tcp
  + eth0 IPv4 Juan                                          _daap._tcp           local
  + eth0 IPv4 civodul                                       _daap._tcp           local
  + eth0 IPv4 Marc                                          _daap._tcp           local
  Failed to resolve service 'Juan' of type '_daap._tcp' in domain 'local': Timeout reached
  Failed to resolve service 'civodul' of type '_daap._tcp' in domain 'local': Timeout reached
  Failed to resolve service 'Marc' of type '_daap._tcp' in domain 'local': Timeout reached
  Got SIGINT, quitting.

  $ sudo /etc/init.d/avahi-daemon restart
  Restarting Avahi mDNS/DNS-SD Daemon: avahi-daemon.

  $ avahi-browse -rk _daap._tcp
  + eth0 IPv4 Marc                                          _daap._tcp           local
  = eth0 IPv4 Marc                                          _daap._tcp           local
     hostname = [XXX]
     address = [XXX]
     port = [3689]
     txt = [XXX]
  + eth0 IPv4 Juan                                          _daap._tcp           local
  = eth0 IPv4 Juan                                          _daap._tcp           local
     hostname = [YYY]
     address = [YYY]
     port = [3689]
     txt = [YYY]
  [...]


(All three commands were executed within a few second time-slot.)
The problem typically reappears hours after the daemon was restarted.

Is it something that other people already experienced?  If not, how can
I provide more useful information?

I'm using the latest version available in Debian unstable, which is
0.6.12.

Thanks,
Ludovic.