notfound 392813 0.8-6.1
stop
Hi Stefan,
On Wed, Dec 27, 2006, Stefan Fritsch wrote:
> package libnss-mdns
> found 392813 0.8-6.1
I would prefer you to open a separate bug report or perhaps we can
clone this one for now. The original bug report is about a broken
behavior after "upgrade to libnss-mdns 0.8-5", but I think I've
addressed this particular issue in my 0.8-6.1 NMU. If you prefer not
to file a new bug, I can clone the bug and retitle it appropriately.
Now to get to your particular problem:
> Update from 0.8-6 to 0.8-6.1 broke DNS for me again. libnss-mdns must
> not edit nsswitch.conf if "local" is exists in the "search" line in
> resolv.conf or remove the "local" or at least give some warning.
It seems to me your site is using the .local TLD; this is sadly an
inherently problematic situation in combination with mDNS and you
should consider changing to a different TLD if you want to use mDNS.
I imagine this might not be an easy thing to achieve, and we have built
a workaround in the nss-mdns + avahi-daemon packages to "support" these
situations (by disabling mDNS lookups).
The solution you describe might sound like a good thing to do for
setups similar to yours, but the problem is a bit more complex once you
start considering roaming laptops which attach to different networks,
which might or might not use the .local TLD.
Since version 0.8-6.1, nss-mdns is configured to systematically contact
avahi-daemon for mDNS lookups; if avahi-daemon isn't running, the
lookup should fail fast. avahi-daemon ships an ifupdown hook since
version 0.6.16-1 which will disable avahi-daemon when a .local TLD is
detected.
The intent of this layout is to check for the existence of a .local TLD
after each change in the DNS (which will typically involve a networking
change).
Stefan, could you report the version of avahi-daemon you had when you
experienced the bug? Is the bug still present in version 0.6.16-1?
If the bug is still present, could you check whether the ifupdown
avahi hook works as expected? This can be achieved by reporting the
output of:
host -t soa local.
Perhaps the test needs to be enhanced to match your particular
configuration; I imagine this can be caused by .local entries in your
/etc/hosts but no real .local DNS zone at your DNS server.
You might also find this page of interest to understand the problem:
http://avahi.org/wiki/AvahiAndUnicastDotLocal
Bye,
--
Loïc Minier <[EMAIL PROTECTED]>
