On Tuesday 02 January 2007 18:58, Loïc Minier wrote: > On Tue, Jan 02, 2007, Stefan Fritsch wrote: > > When I did the upgrade I had avahi-daemon 0.6.15-2 installed. > > The problem is still there with avahi-daemon 0.6.16-1, when I > > change nsswitch.conf to the configuration added by libnss-mdns. > > Ah. Is avahi-daemon running after a networking restart?
Yes. Stopping avahi-daemon manually is another way to fix the problem. This could also be recommended as a quick workaround if there are any problems. > > > I don't use .local TLD anymore, but I used it in the past, so > > that the entry in the resolv.conf was still there. The "search > > local" entry *alone* prevents DNS from working, it is not > > necessary to have .local anywhere in DNS or /etc/hosts. > > That's very interesting; actually, a new upstream release of > nss-mdns just came out and it precisely targets .local in the > "search" entry of resolv.conf. The new upstream release defaults > to ignoring the search field completely. Maybe this could be backported to the version in etch? This would be an elegant solution for the "search local" problem, IMHO. > > > Some more thoughts: > > - dnsmasq which is used on the openWRT routers by default will > > not return SOA records, even if it serves A records: > > That's interesting. Does it use the .local TLD or must it be > configured to do so? > > Do you see a way to detect such a configured openWRT router? Does > it add ".local" in the resolv.conf of the DHCP client? > > This might be an useful test to add aside of the avahi SOA lookup. No, it doesn't do anything with .local by default. The default domain is .lan, which should be save. It just serves its own /etc/hosts as DNS A records. So there would only be a problem if someone puts a host.local entry there. > > - I consider it very unexpected behaviour for a package to modify > > a file in /etc without asking. Policy 10.7.3 says: "local changes > > must be preserved during a package upgrade". After the upgrade to > > 0.8-5 I changed nsswitch.conf to not use mdns but my change was > > overwritten on upgrade to 0.8-6.1. Maybe a debconf note or > > NEWS.Debian entry would be in order. Or maybe libnss-mdns should > > remember that it changed nsswitch.conf once already and not touch > > it again. > > libnss-mdns should not change resolv.conf for you again. The full If it is only changed once on upgrade from sarge it should be ok. > I'll try to prepare the new upstream release of nss-mdns and send > it to you for testing; I expect it will solve the problem. Yes, please. Cheers, Stefan
