Thank you for your answers.
In my log bind start like that:
starting BIND 9.2.2-P3 -u named -t /var/named/chroot
I think this meaning that bind start in chroot directory.
I try in name.custom
## named.custom - custom configuration for bind
#
# Any changes not currently supported by redhat-config-bind should be
put
# in this file.I try with :
options {
directory "/var/named";
};
Always the same.
...
Jean-François
-----Message d'origine-----
De : fedora-list-admin@xxxxxxxxxx [mailto:fedora-list-admin@xxxxxxxxxx]
De la part de Christopher K. Johnson
Envoyé : jeudi 12 février 2004 19:00
À : fedora-list@xxxxxxxxxx
Objet : Re: RE : bind : zone file not found
sid wrote:
>this is long but here is how my dns is configure.
>bind-chroot-....rpm made the directories
>and I used redhat-config-bind to do this config.
>
>
>/var/named/chroot
>
> /dev/null
> random
>
> /etc/localtime
> named.conf
> named.custom
> mdc.key
>
> /var/named/0.0.127.in-addr.arpa.zone
> 0.168.192.in-addr.arpa.zone
> localhost.zone
> sid.local.zone
>
>
>
[SNIP]
Do you have an options section like the following in your named.conf?
If not then you need one. Otherwise bind is looking for
/var/named/chroot/sid.local.zone etc. instead of
/var/named/chroot/var/named/sid.local.zone etc.
options {
directory "/var/named";
};
--
-----------------------------------------------------------
"Spend less! Do more! Go Open Source..." -- Dirigo.net
Chris Johnson, RHCE #807000448202021
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
