From RHEL to CentOS BIND 9
Kirk Bradel
kirkb at kirkb.net
Wed Dec 5 19:51:34 UTC 2007
isplist at logicore.net wrote:
> I do see some 192 info I need to remove in there. The server won't start at
> all.
>
>> What rpm / rpm's did you install.
>
> bind-9.3.3-10.el5
>
>> Can you please post the contents of named.conf
>
> options {
> directory "/var/named";
> dump-file "/var/named/data/cache_dump.db";
> statistics-file "/var/named/data/named_stats.txt";
> pid-file "/var/run/named/named.pid";
> recursion no;
>
> forwarders {
> 127.0.0.1;
> };
> allow-transfer {
> xx.xx.xx.31;
> };
> };
>
> controls {
> inet * port 953 allow {
> 127.0.0.1;
> }
> keys {
> rndc-key;
> };
>
> // Note: the following will be supported in a future release.
> /*
> host { any; } {
> topology {
> 127.0.0.0/8;
> };
> };
>
> zone "." {
> type hint;
> file "named.root";
> };
>
> zone "0.0.127.IN-ADDR.ARPA" {
> type master;
> file "localhost.rev";
> };
>
> zone "domain.com" {
> type slave;
> file "s/domain.com.bak";
> masters {
> 192.168.1.1;
> };
> };
>
> zone "0.168.192.in-addr.arpa" {
> type slave;
> file "s/0.168.192.in-addr.arpa.bak";
> masters {
> 192.168.1.1;
> };
> };
> */
>
> zone "xxx.com" {
> type slave;
> file "xxx.com";
> allow-transfer {
> xx.xx.xx.31;
> xx.xx.xx.50;
> common-allow-transfer;
> };
> masters {
> xx.xx.xx.31;
> };
> };
> zone "67.in-addr.arpa" {
> type master;
> file "67.in-addr.arpa";
> allow-transfer {
> common-allow-transfer;
> };
> };
> zone "10.98.67.in-addr.arpa" {
> type master;
> file "10.98.67.in-addr.arpa";
> allow-transfer {
> common-allow-transfer;
> };
> };
> acl common-allow-transfer {
> none;
> };
>
> key rndc-key {
> algorithm hmac-md5;
> secret "xxxxxxxxxxxxxxxxxxxxxxxx";
> };
> server xx.xx.xx.31; {
> };
>
>
>> Can you please post the contents of /etc/sysconfig/named
>
> ROOTDIR=/var/named/chroot
>
>
>
Mike,
According to your notes above, you *didn't* install the bind-chroot package or
else you would have a package like this "bind-chroot.i386".
Your /etc/sysconfig/named file indicates that BIND should be running chroot.
However, none of the entries in the named.conf file point to that chroot
directory structure.
More information about the bind-users
mailing list