Bind Problem

[gwichman]

Having trouble getting Bind to start properly. Yes it was installed with FC2. Appreciate any help..

The problem:

Jul 29 16:40:04 killians named[10828]: starting BIND 9.2.3 -u named -t /var/named/chroot
Jul 29 16:40:04 killians named[10828]: using 1 CPU
Jul 29 16:40:04 killians named[10828]: loading configuration from '/etc/named.conf'
Jul 29 16:40:04 killians named[10828]: listening on IPv4 interface lo, 127.0.0.1#53
Jul 29 16:40:04 killians named[10828]: listening on IPv4 interface eth0, 10.1.1.12#53
Jul 29 16:40:04 killians named[10828]: command channel listening on 127.0.0.1#953
Jul 29 16:40:04 killians named[10828]: zone 221.6.24.in-addr.arpa/IN: loading master file 221.6.24.in-addr.arpa.zone: file not found
Jul 29 16:40:04 killians named[10828]: zone hockeyratings.com/IN: loading master file hockeyratings.com.zone: file not found
Jul 29 16:40:04 killians named[10828]: running
Jul 29 09:40:05 killians named: named startup succeeded

Various files:

[root@killians etc]# cat /etc/sysconfig/named
# Currently, you can use the following options:
# ROOTDIR="/some/where" -- will run named in a chroot environment.
# you must set up the chroot environment before
# doing this.
# OPTIONS="whatever" -- These additional options will be passed to named
# at startup. Don't add -t here, use ROOTDIR instead.
ROOTDIR=/var/named/chroot


[root@killians etc]# cat /var/named/chroot/etc/named.conf
controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};

zone "." IN {
type hint;
file named.ca";
}

zone "hockeyratings.com" {
type master;
file "hockeyratings.com.zone";
};
zone "221.6.24.in-addr.arpa" {
type master;
file "221.6.24.in-addr.arpa.zone";
};

include "/etc/rndc.key";


[root@killians etc]# ls -ltr /var/named/chroot/etc/
total 8
-rw-r----- 1 root named 132 Jul 24 11:00 rndc.key
-rw-rw-r-- 1 named named 305 Jul 29 09:45 named.conf


[root@killians etc]# ls -ltr /var/named/chroot/var/named/
total 20
-rw-r--r-- 1 root root 433 Jul 24 11:14 named.local
-rw-r--r-- 1 root root 2518 Jul 24 11:14 named.ca
-rw-r--r-- 1 root root 195 Jul 24 11:14 localhost.zone
-rw-rw-r-- 1 named named 388 Jul 25 14:16 hockeyratings.com.zone
-rw-rw-r-- 1 named named 227 Jul 25 14:16 221.6.24.in-addr.arpa.zone


[root@killians etc]# cat /var/named/chroot/var/named/hockeyratings.com.zone
$TTL 86400
dns1.hockeyratings.com. IN SOA localhost gwichman (
28 ; serial
28800 ; refresh
14400 ; retry
3600000 ; expire
86400 ; ttl
)



killians IN A 24.6.221.74
www IN CNAME killians.hockeyratings.com.
ftp IN CNAME killians.hockeyratings.com.
dns1 IN CNAME killians.hockeyratings.com.
dns1 IN NS 24.6.221.74
mail IN MX 1 killians.hockeyratings.com.


[root@killians etc]# cat /var/named/chroot/var/named/221.6.24.in-addr.arpa.zone
$TTL 86400
dns1.hockeyratings.com. IN SOA localhost gwichman (
5 ; serial
28800 ; refresh
14400 ; retry
3600000 ; expire
86400 ; ttl
)



74 IN PTR killians.hockeyratings.com.
24.6.221.74 IN NS dns1

[jeru]

first /etc/named.conf doesn't mean anything, you can delete that file


try adding something like this to /var/named/chroot/etc/named.conf
options {
directory "/var/named";
};

Otherwise manually specify the file path each time. (relative to the chroot enviroment since that is all named knows about and can access)

[gwichman]

Excellent thanks. That statement solved my problem. I have a new problem now though.. I'll read my Bind book over the weekend but if anyone knows what i'm doing wrong here is the problem:

Jul 30 14:50:10 killians named[13218]: starting BIND 9.2.3 -u named -t /var/named/chroot
Jul 30 14:50:10 killians named[13218]: using 1 CPU
Jul 30 14:50:10 killians named[13218]: loading configuration from '/etc/named.conf'
Jul 30 14:50:10 killians named[13218]: listening on IPv4 interface lo, 127.0.0.1#53
Jul 30 14:50:10 killians named[13218]: listening on IPv4 interface eth0, 10.1.1.12#53
Jul 30 14:50:10 killians named[13218]: command channel listening on 127.0.0.1#953
Jul 30 14:50:10 killians named[13218]: dns_master_load: 221.6.24.in-addr.arpa.zone:2: dns1.hockeyratings.com: not at top of zone
Jul 30 14:50:10 killians named[13218]: zone 221.6.24.in-addr.arpa/IN: loading master file 221.6.24.in-addr.arpa.zone: not at top of zone
Jul 30 14:50:10 killians named[13218]: dns_master_load: hockeyratings.com.zone:2: dns1.hockeyratings.com: not at top of zone
Jul 30 14:50:10 killians named[13218]: zone hockeyratings.com/IN: loading master file hockeyratings.com.zone: not at top of zone
Jul 30 14:50:10 killians named[13218]: running
Jul 30 07:50:10 killians named: named startup succeeded

[puravida]

Excellent thanks. That statement solved my problem. I have a new problem now though.. I'll read my Bind book over the weekend but if anyone knows what i'm doing wrong here is the problem:

Jul 30 14:50:10 killians named[13218]: starting BIND 9.2.3 -u named -t /var/named/chroot
Jul 30 14:50:10 killians named[13218]: using 1 CPU
Jul 30 14:50:10 killians named[13218]: loading configuration from '/etc/named.conf'
Jul 30 14:50:10 killians named[13218]: listening on IPv4 interface lo, 127.0.0.1#53
Jul 30 14:50:10 killians named[13218]: listening on IPv4 interface eth0, 10.1.1.12#53
Jul 30 14:50:10 killians named[13218]: command channel listening on 127.0.0.1#953
Jul 30 14:50:10 killians named[13218]: dns_master_load: 221.6.24.in-addr.arpa.zone:2: dns1.hockeyratings.com: not at top of zone
Jul 30 14:50:10 killians named[13218]: zone 221.6.24.in-addr.arpa/IN: loading master file 221.6.24.in-addr.arpa.zone: not at top of zone
Jul 30 14:50:10 killians named[13218]: dns_master_load: hockeyratings.com.zone:2: dns1.hockeyratings.com: not at top of zone
Jul 30 14:50:10 killians named[13218]: zone hockeyratings.com/IN: loading master file hockeyratings.com.zone: not at top of zone
Jul 30 14:50:10 killians named[13218]: running
Jul 30 07:50:10 killians named: named startup succeeded



Hi,

I have the exact same problem with the date. I'm not sure but I think it affects the logrotate daemon too, has anybody found a fix for this weird date problem ? You see that it seems to switch to UT (Universal Time) when processing some routines and then revert back to the system date.

Regards,

[donrob]

I get the same. Did anybody resolve this?

Also, using the Fedora DNS config tool wipes out most of the configuration.

don