Hi Matthew, Thanks for getting back to me. Forgive me for asking this, but seeing that your procedure is so blantantly different to what is suggested in *both* books, is something actually wrong in those book?
I mean.., what I'm being told to do in both the Handbook as well as FBSD Unleashed., is nothing like what you have suggested here., I'm only trying to have things as secure - but standardized as much as I can on the machine. Thanks for the time, I'd appreciate you (and others') view on what *is* supposed to be the standard procedure for running bind in a sandbox. Stacey On Sun, 2002-07-14 at 11:31, Matthew Seaman wrote: > On Sun, Jul 14, 2002 at 10:50:54AM +0100, Stacey Roberts wrote: > > > I'm trying to set named up on a box here, following the handbook as > > well as FBSD Unleashed - but I cannot seem to get bind started and going > > in a sandbox. > > > > This is the error I keep getting: > > # /usr/sbin/named -u bind -g bind -t /etc/namedb/s/ > > can't open '/etc/namedb/named.conf' > > # > > If your named.conf file is in the usual place, /etc/namedb/named.conf, > then it's going to be inaccessible to named once it's performed the > chroot(2) to /etc/named/s > > You need to replicate all of the file structure of /etc/namedb to your > chroot directory. Try this: > > mkdir /var/named > cd / > tar -cf - etc/namedb | (cd /var/named ; tar -xvpf - ) > > Now when you start up named, use the command line: > > /usr/sbin/named -u bind -g bind -t /var/named > > named should then be happily reading the file > /var/named/etc/namedb/named.conf thinking that it's actually /etc/named.conf > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks > Savill Way > Tel: +44 1628 476614 Marlow > Fax: +44 0870 0522645 Bucks., SL7 1TH UK -- Stacey Roberts B.Sc. (HONS) Computer Science Network Systems Engineer
signature.asc
Description: This is a digitally signed message part
