On 2011/07/23 08:25, Nico Kadel-Garcia wrote:
On Sat, Jul 23, 2011 at 2:14 AM, Todd And Margo Chester
<[email protected]> wrote:
On 07/22/2011 10:41 PM, Nico Kadel-Garcia wrote:
Youve got named running in the chrooted environment in
/var/named/chroot. Yank out the bind-chroot package for now, restorie
it when you've had a chance to read and review the documentaiton.
Hi Nico,
When I had originally ported, I copied the computer directory tree
/var/named/chroot
This looks like part of your problem. When you "copied" it, did your
copying preserve ownership of all the files? Did you use tar, rsync,
scp, or what?
over from the old computer. I did not have bind-chroot installed,
so of course, bind could not find anything. Then I remembered
chroot, so I yum'ed bind-chroot.
But you'd already copied over the material, and probably tried to
merge /etc/named contents on top of your already written material.
Chaos ensued.
And there is a possibility that an "ls --lcontext /var/named" command
will reveal secondary problems with the files having the wrong
security context. That bit me porting over my named setup from an
old Fedora machine. Along the way I edited the files to clean up
some of the way they work. That involved adding a couple files. Those
two files refused to work until I fixed the security context on them.
{^_^}
