Minimal distribution of BIND binaries
Jim Reid
jim at mpn.cp.philips.com
Wed Oct 13 09:39:58 UTC 1999
>>>>> "James" == James Hall-Kenney <JHall at sytec.co.nz> writes:
James> I want to reduce the distribution set to just necessary server file
James> and client files. At the moment the file set I have:
James> ./bin
James> nslookup
James> dig
James> ./lib
James> libbind.a
James> libbind.r.a
James> nslookup.help
James> ./sbin
James> named
James> ndc
James> This seems to work OK - any issues with only sending these files
James> (+ config files ...).
You forgot named-xfer. Without that, your name servers won't be able
to slave any zones. There are also "interesting" problems if you use a
version of named-xfer that's from a different release of BIND. And
personally, I prefer dig to nslookup. You can probably get away
without shipping libbind.a unless you plan on linking stuff on the
remote servers with an up to date resolver library. Still it won't
hurt to make the code available on these systems even if nothing uses
it.
James> I was unable to work out what ./sbin/irpd was - still can't make
James> the man pages properly ;).
You don't need it. irpd is the ISC's equivalent of Sun's nscd. It
reads (and caches) the contents of things like /etc/services and
provides a host lookup API that can switch between /etc/hosts, the DNS
and NIS.
More information about the bind-users
mailing list