Bind 8.2.3 on Solaris and CHROOT

[Mark.Andrews at nominum.com]

	I generally advise people to follow the instructions in
	ftpd(8) on how to setup a chroot area.  These should match
	the OS and its release.

	The malloc errors are most probably because /dev/zero is missing
	from the chroot area.

	-t causes the sever to change to directory given and make it
	the new root.

	Mark

> We are running Bind 8.2.3 on Solaris 7 and have been trying to get it to
> work in a chroot "jail"... We have followed instructions in the Langfeldt
> Que Book (DNS and Bind) - well more or less, and we have found that named
> seems to start ok, but there are problems with named-xfer.  Specifically, we
> get "malloc" errors whenever named-xfer is invoked.
> 
> We found a cached page on Google for what seems to be a similar error report
> (at
> http://www.google.com/search?q=cache:archives.neohapsis.com/archives/sf/sun/
> 2000-q2/att-0216/01-bind-chroot.html+named-xfer+malloc&hl=en )
> but we did not see any followup to this that included success...
> 
> Anyone have any insight in this whole process?  We have seen conflicting
> advice on whether or not to create /dev/tcp and /dev/udp in the chrooted
> jail, (we dont think that is necessary from our testing)  and I guess we are
> also wondering what the -t option on named startup really is doing.
> 
> TIA for any insight/advice.
> 
> --
> ===============================
> Kerry Liles (Mr. for the gender curious)
> Network Security Analyst
> Software Spectrum Inc.
> 
>    kerry.liles AT softwarespectrum.com
>    NOT whatever is in the reply-to
> ===============================
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com