On Sep 24, 2010, at 12:51 PM, Tony Finch <d...@dotat.at> wrote: > A default build of bind expects to find it in /etc/named.conf > If you are running chrooted it needs to be copied into the chroot.
Most systems these days have packages of BIND. Those that do tend to have BIND-chroot as an option for install. What are the benefits of chrooting BIND? I am about to move my primary NS to a new machine, so I have to build it out. I can build it normal, or chroot. Chrooting doesn't seem much more challenging, though there are some additional gotchas that it adds. Everything must be self contained in the chroot. Some tools like SELinux can make that a tiny bit more work too. I have always wondered, in the case of BIND, what are the pros and cons of going chroot? -- Scott * If you contact me off list replace talklists@ with scott@ * _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
