Am Mi, den 05.05.2004 schrieb Mike McMullen um 18:28:
> This system is also a backup nameserver. I copied the zone db files
> we use from a 7.3 system and brought named up. Everything seems
> to resolve ok.
Your slave zone files hopefully are in
/var/named/chroot/var/named/slaves/ (because of what you wrote in
following paragraph).
> However, named messages in /var/log/messages are time
> stamped 3 hours ahead of the time the system is set to.
Don't you have a file /var/named/chroot/etc/localtime?
> Also, I noticed a chroot directory in the /var/named directory.
> Actually I had to put the db file in /var/named/chroot/var/named
> to get named to work. There is also another chroot directory
> in that directory as well so that:
>
> /var/named/chroot/var/named/chroot/var/named
>
> exists.
>
> Can someone tell me what is going on here?
You did not only install the bind package but bind-chroot too. So bind
is set up to run in chrooted mode. See /etc/sysconfig/named, where the
chroot ROOTDIR is pointing to.
> TIA,
>
> Mike
The named chroot issue was discussed and explained here before, even in
detail. Please search the list archive for more explanations.
I do not know what you mean with your subject line "named Wierdness" -
what is weird? The only thing from your posting which is not normal is
the wrong (?) time in the named.log. Did you change anything with your
timezone or else? I am running bind-chroot on my FC1 server and how no
abnormal issues. It is running like expected.
Alexander
--
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 1 (Yarrow) on Athlon CPU kernel 2.4.22-1.2188.nptl
Sirendipity 20:18:13 up 8 days, 19:06, load average: 0.46, 0.44, 0.37
[ ÎÎÏÎÎ Ï'ÎÏÏÎÎ - gnothi seauton ]
my life is a planetarium - and you are the stars
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
