dns server sizing?

[Barry Margolin]

In article <424.938008074 at kludge.mpn.cp.philips.com>,
Jim Reid  <jim at mpn.cp.philips.com> wrote:
>>>>>> "David" == David Mitchell <davem at fdgroup.co.uk> writes:
>
>    >> I'm not too fond of Solaris as a name server platform because
>    >> of all the nsswitch.conf, DOORS, nscd, nis, nis+, etc cruft
>    >> that gets in the way of quick name/address lookups.
>
>    David> That cruft only affects solaris clients, and has no impact
>    David> on on a Solaris machine acting as a name server.
>
>True: up to a point. But what if those clients are things like dig or
>nslookup or even named-xfer? And how do you know where or what is
>giving them an answer to a host lookup? I suppose someone could
>by-pass all that Solaris cruft by statically linking the name server
>software with libbind.a - no more nsswitch.conf - but why bother with
>that hassle in the first place?

It doesn't matter what the clients are doing.  named doesn't use
nsswitch.conf *ever*.  It doesn't use doors, nscd, NIS, etc.  named on
Solaris is essentially the same as named on any other system.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.