Centos 5.6 - Perfect Server - bind-chroot - error failed

[studiorobert]

Hi!

Great awesome tutorials.. I am doing the Centos 5.6 install on a Centos 5.6 i386 box. I have had a variety of bumps as I go through them, but the first one I cannot solve is this: the chrooted bind will just not start.

here is my output when running "/etc/init.d/named start"

Starting Named:
Error in named configuration:
/var/named/chroot/var/named/named.local 1: unknown option '$ttl'
/var/named/chroot/var/named/named.local 3: unknown option 'Serial'
/var/named/chroot/var/named/named.local 4: unknown option 'Refresh'
/var/named/chroot/var/named/named.local 5: unknown option 'Retry'
/var/named/chroot/var/named/named.local 6: unknown option 'Expire'
/var/named/chroot/var/named/named.local 7: unknown option 'Minimum'
/etc/named.conf:30: unexpected token near end of file
                         [ FAILED ]

[javamacion]

I have same error, please help.
I test and quit the comments in /var/named/chrooot/var/named/named.local
but the error in $ttl appears

[studiorobert]

javamacion,

I actually never succeeded in finishing the tutorial.

I got Bind to run non CHROOT, then i experimented a bit with ISPCONFIG..

I actually just formatted my Centos machine and reinstlaled stock centos.. I am going to be doing the whole tutorial again.


I went to #bind on... Whatever IRC network they use... And was thoroughly belittled by the people there...Then I read about 100 pages from a O'Rielly book about Bind...

It appears there are probably problems with the location of the example files the tutorial has us edit.. And then also problems within those example files...

[falko]

Which tutorial exactly (URL) did you use?

What's in /var/named/chroot/var/named/named.local?

[javamacion]

this is the tutorial link i'm doing, when I install bind-Chroot and run is the error
http://www.howtoforge.com/perfect-se...ispconfig-3-p5



in /var/named/chroot/var/named/named.local appears the error

Starting Named:
Error in named configuration:
/var/named/chroot/var/named/named.local 1: unknown option '$ttl'
/var/named/chroot/var/named/named.local 3: unknown option 'Serial'
/var/named/chroot/var/named/named.local 4: unknown option 'Refresh'
/var/named/chroot/var/named/named.local 5: unknown option 'Retry'
/var/named/chroot/var/named/named.local 6: unknown option 'Expire'
/var/named/chroot/var/named/named.local 7: unknown option 'Minimum'
/etc/named.conf:30: unexpected token near end of file

I think it dont recognise the ";" comments.

[falko]

What's in /var/named/chroot/var/named/named.local?

[studiorobert]

Falko,

I am now in the middle of re-doing the tutorial.. I am, as noted, doing the tutorial on a i386 pentium 4 based machine... I will post my experience here, along with any changes to the tutorial I make in order to get i386 packages installed.. Most of the tutorial is exactly the same, but there are a few packages that need to be i386....


One huge question I have is how BIND CHROOT works.. I have, for example, 5 static IPS available, and want to use two for dedicated name servers - but do not quite understand how IPCONFIG will be working once installed...

Does it modify the BIND files to add more domain routings? Does it append a config file, what does it do?

Thanks!

[javamacion]

Hi falko, in /var/named/chroot/var/named/named.local
is:

$TTL 86400
@ IN SOA ns1.sizne.com. root.localhost. (
                                                  1997022700;
                                                   28800;
                                                   14400;
                                                    3600000;
                                                   86400);
    IN     NS     localhost.
1    IN     PTR    localhost.

Thanks for your help

[falko]

Originally Posted by studiorobert

Does it modify the BIND files to add more domain routings? Does it append a config file, what does it do?

Thanks!

ISPConfig normally just writes to the named.conf.local files and adds/modifies/deletes the zone files referenced in named.conf.local.

[falko]

@javamacion: Can you please open a new thread? This is too confusing if two people post their problems in one thread. Thanks!