[Pkg-utopia-maintainers] Bug#392813: looking at this bug..

[Walter Hofmann]

On Sat, Oct 14, 2006 at 10:10:15PM +0200, Lennart Poettering wrote:
> 
> As I already wrote in my last email, the "search local" is indeed the
> problem.
> 
> It is explicitly *not recommended* to use "search local". If people
> choose to use it it's their problem.
> 
> "search local" has lots of problems. This one is only one of them.
> 
> The "search local" functionality is *only* useful in setups where 
> traditional DNS is not used *at all*. In all other cases, don't use
> it, it causes all kinds of problems and will slow down all lookups. I
> am really surprised that so many people actually make use this
> configuration option. I never documented it for nss-mdns. Only a minor
> entry in my changelog even mentions it.
> 
> To stress this once more:
> 
> DO NOT USE "search local" UNLESS YOU REALLY KNOW WHAT YOU DO! And if
> you do use it, don't file bugs about it. I am fully aware that it is
> problematic. 


I read between the lines that the .local domain is something special for 
nss-mdns!?

As I wrote earlier, I don't use mdns at all. I taught bind (which runs 
at 127.0.0.1) that it is authorative for .local and resolving works just 
fine. It doesn't slow down other queries much as it is running locally 
and is authorative for .local.

But I definitely need "search local" in resolv.conf. Otherwise, random 
services on this machine will break because I didn't enter the fqdn in 
many places.

But somehow, problably due to some dependency or recommendation, 
nss-mdns got installed on my system and gets in bind's way.

So whether nss-mdns does or doesn't support "search local" is of no 
concern to me -- I just doesn't want it to interfere with my otherwise 
working setup.

Walter