mnichols62
Verified User
- Joined
- Mar 13, 2007
- Messages
- 12
Running RHEL 4.
Foolishly ran up2date on bind. The rpm moved my bind world to a chroot environment. I made most of the modifications listed in other posts to get directadmin to point to /var/named/chroot as the ROOTDIR for all dns operations, however, I still have at least one problem.
directadmin creates the domainname.com.db files as root. In order for bind to read them in the chroot environment they need to be owned by named:named.
Is there a place I can update the directadmin domain_add and related scripts to set ownership after domain creation to named:named?
My other alternative would be to reverse the chroot environment or do a reinstall of the directadmin bind. Both options seem risky.
Foolishly ran up2date on bind. The rpm moved my bind world to a chroot environment. I made most of the modifications listed in other posts to get directadmin to point to /var/named/chroot as the ROOTDIR for all dns operations, however, I still have at least one problem.
directadmin creates the domainname.com.db files as root. In order for bind to read them in the chroot environment they need to be owned by named:named.
Is there a place I can update the directadmin domain_add and related scripts to set ownership after domain creation to named:named?
My other alternative would be to reverse the chroot environment or do a reinstall of the directadmin bind. Both options seem risky.
