BIND 8.24 & Solaris 7

[Kevin Darcy]

june wrote:

> Hi, Newbiee here.
>
> I installed Bind 8.24 following these directions on a Solaris 7 system:
>
> Building
>
>         If you do not have an ANSI/ISO C compiler, give up or get GCC.  The
>         one exception is the ULTRIX compiler, which isn't full ANSI C but it
>         has function prototypes and BIND works around the rest.  BIND 8 also
>         wants a C library that's ANSI/ISO standard, although it can work
>         around some common failings.
>
>         If you do not have yacc, get byacc or GNU bison.  If you do not have
>         lex, get GNU flex.  For information on where to get GNU software,
> see
>         http://www.fsf.org/order/ftp.html.
>
>         If you want to build outside the source pool, then
>
>                 make DST=/your/destination/here SRC=`pwd` links
>                 cd /your/destination/here
>
>         If you want to use DST=/var/obj/bind, you can simply type
>
>                 make stdlinks
>
>         Next, make sure you have no stale trash laying about
>
>                 make clean
>
>         Then, update the Makefile dependencies:
>
>                 make depend
>
>         NOTE: "make depend" is a NO-OP for some platforms, but always
> harmless.
>
>         Finally,
>
>                 make all
>
> Installation
>
>         To install, type
>
>                 make install
>
>         This will copy binaries to the appropriate locations for your
> system,
>         and install the BIND 8 library and header files under
> /usr/local/bind.
>
> Now what? I'm sort of confused of where to go next?  Does this mean it has
> been installed?

Probably. But probably *not* where your OS expects it to be. The default
/etc/rc2.d/S72inetsvc on Solaris will start up /usr/sbin/in.named, but I think
BIND 8's default install location is /usr/local/sbin/named, even on Solaris (go
figure). You have a number of options here.

If you *don't* want /usr/local/sbin on your box, you can either

1) Copy the named binary to /usr/sbin/in.named and named-xfer to
/usr/sbin/named-xfer, then set the "named-xfer" option in named.conf to
/usr/sbin/named-xfer

or

2) Go back and rebuild/reinstall BIND with non-default pathnames, i.e.
/usr/sbin/in.named and /usr/sbin/named-xfer

If you don't care about running stuff from /usr/local/sbin, then you have a
couple more options:

3) Link /usr/sbin/in.named to the installed pathname for named

or

4) Hack the installed pathname into /etc/rc2.d/S72inetsvc

Note that *all* of these options are subject to breakage if you install an
OS patch that decides to overwrite one or more of your system files with the
"correct" version. Solaris patches are notorious for that.


- Kevin