Am Di, den 23.12.2003 schrieb Sturla Holm Hansen um 02:49:
> /etc/named.conf
No, he is right that the named.conf resides in /var/named/chroot/etc/ If
he uses the chrooted bind. See the init script checks:
# Check that networking is up.
[ "${NETWORKING}" = "no" ] && exit 0
[ -r /etc/sysconfig/named ] && . /etc/sysconfig/named
[ -x /usr/sbin/named ] || exit 0
[ -r ${ROOTDIR}/etc/named.conf ] || exit 0
> On Mon, 2003-12-22 at 02:28, Hong Siew wrote:
> > Starting named from redhat-config-services shows no errors. However,
> > the zones were not loaded. Using tail –f /var/log/messages shows that
> > the zone files were not found. The zone files were definitely in
> > /var/named/chroot/var/named folder.
> >
> >
> >
> > Where and which file do I need to check or modify so that the named
> > knows where the zone files are located.
> >
> >
> >
> > Thanks
So be sure what is set up in /etc/sysconfig/named
(ROOTDIR=/var/named/chroot) and that the permissions of all files are
correct set.
For me the chrooted named configuration works fine. I only made the zone
files by hand and did not use the redhat-config tool.
Alexander
--
Alexander Dalloz | Enger, Germany
PGP key valid: made 13.07.1999
PGP fingerprint: 2307 88FD 2D41 038E 7416 14CD E197 6E88 ED69 5653
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
