On Sat, Feb 16, 2008 at 01:36:15PM +0100, Lennart Poettering wrote: > On Sat, 16.02.08 13:06, Mike Hommey ([EMAIL PROTECTED]) wrote: > > > > Try Google. Try reading docs. Try reading mailing list archives. > > > > > > This has been discussed a million times already on various places. > > > > A million times ? Googling for mdns4_minimal mdns_minimal return only 3 > > pages > > or results, which, by google standards, is pretty few. And the only > > reference > > to mdns_minimal being a problem instead of mdns4_minimal is a bug report > > where > > *YOU* were only ranting. And a bunch of the other results are... *this* bug. > > > > So please support your point with better arguments. > > So, let's see what the README/web site of nss-mdns says about this problem: > > <snip> > libnss_mdns.so.2 resolves both IPv6 and IPv4 addresses, > libnss_mdns4.so.2 only IPv4 addresses and libnss_mdns6.so.2 only IPv6 > addresses. Due to the fact that most mDNS responders only register > local IPv4 addresses via mDNS, most people will want to use > libnss_mdns4.so.2 exclusively. Using libnss_mdns.so.2 or > libnss_mdns6.so.2 in such a situation causes long timeouts when > resolving hosts since most modern Unix/Linux applications check for > IPv6 addresses first, followed by a lookup for IPv4. > </snip>
Avahi default, at least in debian, is to register IPv6 addresses. As for delays, they should be considered bugs as with the glibc. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
