Subject: Re: HEADS UP: nsswitch about to go `live' in NetBSD-current
To: Jason Thorpe <thorpej@nas.nasa.gov>
From: Andrew Brown <twofsonet@graffiti.com>
List: current-users
Date: 01/19/1999 15:42:46
>The correct semantics an be achieved with:
>
>	hosts: dns [notfound=return unavail=continue success=return] files
>
>...and since "unavail=continue" and "success=return" are implied (see the
>nsswitch.conf(5) manual page), it can simply be expressed as:
>
>	hosts: dns [notfound=return] files

but will this actually give the current/desired behavior?  ie, if you
nslookup 10.0.0.1 (borrowed a little from your example), if the dns is
available, you *will* get an authoritative nxdomain answer.

however...your /etc/hosts file knows better, doesn't it?

and mine does too.  there's one host i connect to more than anything
else, and i call it "home".  however, home.whereever.iam.com never
exists, and i can always guarantee that i'll get an authoritative
negative answer for it.  but i do have a home.

so isn't the current behavior more like

	hosts: dns [notfound=continue unavail=continue success=return] files

???

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."