in.named not recognizing new build of bind

[Peter Ziemann]

David,

BIND will typically install itself in /usr/local/sbin. The file name is
"named" and not
"in.named" which seems to be part of the Solaris7 distribution.

Therefore just to test, kill the in.named process and run named from the
directory
/usr/local/sbin. Please be aware that named.conf is required to be in
/usr/local/etc
instead of /etc (or you start it with the -f /etc/named.conf option).

Ones you have successfully performed that task you have to modify the
start-up
files in /etc/rc*.d/*. It is the best to grep for in.named and change the
lines to
/usr/local/sbin/named.

Regards,

Peter Ziemann, hostmaster at pziemann.de

David Schlussel <dschluss at slip.net> wrote in message
news:Pine.GSO.3.96.1000301150350.26160E-100000 at slip-3.slip.net...
>
> I've successfully built bind.8.2.2 on solaris7, all the makes ran without
> error, but when I run /usr/sbin/in.named, my /var/adm/messages pops out
>
> named[456]: starting.  in.named BIND 8.1.2 Tue Nov 10 18:16:24 PST 1998
>
> how do i get named to recognize the new bind?  do i have to rebuild that?
>
> -David
>
>      _.'`._.'`._.'`._.'`._.'`._.'`._.'`._.'`._
>    .'                                         `.
>    |   David - http://www.slip.net/~dschluss   |
>    `._    _    _    _    _    _    _    _    _.'
>       `..' `..' `..' `..' `..' `..' `..' `..'
>
>
>
>