Hi !!
I am configuring Bind 9 on Redhat 7 but unable to start the named.
Here is my /var/log message log:
Feb 20 09:49:58 ns2 named[2003]: starting BIND 9.0.0
Feb 20 09:49:58 ns2 named[2005]: loading configuration from
'/var/named/named.bo
ot'
Feb 20 09:49:58 ns2 named[2005]: the default for the 'auth-nxdomain'
option is n
ow 'no'
Feb 20 09:49:58 ns2 modprobe: modprobe: Can't locate module net-pf-10
Feb 20 09:49:58 ns2 named[2005]: no IPv6 interfaces found
Feb 20 09:49:58 ns2 named[2005]: listening on IPv4 interface lo,
127.0.0.1#53
Feb 20 09:49:58 ns2 named[2005]: socket.c:1183: unexpected error:
Feb 20 09:49:58 ns2 named[2005]: setsockopt(10, SO_TIMESTAMP) failed
Feb 20 09:49:58 ns2 named[2005]: listening on IPv4 interface eth0,
209.58.33.71#
53
Feb 20 09:49:58 ns2 named[2005]: socket.c:1183: unexpected error:
Feb 20 09:49:58 ns2 named[2005]: setsockopt(12, SO_TIMESTAMP) failed
Feb 20 09:49:58 ns2 named[2005]: socket.c:1183: unexpected error:
Feb 20 09:49:58 ns2 named[2005]: setsockopt(9, SO_TIMESTAMP) failed
Feb 20 09:49:58 ns2 named[2005]: dns_master_load: db.127.0.0:1: no TTL
specified
Feb 20 09:49:58 ns2 named[2005]: dns_zone_load: zone
0.0.127.IN-ADDR.ARPA/IN: da
tabase db.127.0.0: dns_db_load failed: no ttl
Feb 20 09:49:58 ns2 named[2005]: loading zones: no ttl
Feb 20 09:49:58 ns2 named[2005]: exiting (due to fatal error)
Feb 20 09:50:00 ns2 CROND[2010]: (root) CMD ( /sbin/rmmod -as)
Anyone have an idea how to solve this problem.
Thanx,
Nauman Ansrai
On Mon, 19 Feb 2001, Ansari wrote:
> Hi !!
>
> I am configuring Bind 9 on Redhat 7 but unable to start the named.
> Here is my /var/log message log:
you have a config problem i think.
> Feb 20 09:49:58 ns2 named[2005]: loading zones: no ttl
you need to put:
$TTL <ttl, eg 1D>
at the beginning of each zone file.
oh, you're probably better off asking your questions on a bind
specific list, rather than linux-kernel.
regards,
--paulj
Ansari writes:
>Hi !!
>
>I am configuring Bind 9 on Redhat 7 but unable to start the named.
>Here is my /var/log message log:
>
>
>Feb 20 09:49:58 ns2 named[2003]: starting BIND 9.0.0
>Feb 20 09:49:58 ns2 named[2005]: loading configuration from
>'/var/named/named.bo
>ot'
>Feb 20 09:49:58 ns2 named[2005]: the default for the 'auth-nxdomain'
>option is n
>ow 'no'
>Feb 20 09:49:58 ns2 modprobe: modprobe: Can't locate module net-pf-10
>Feb 20 09:49:58 ns2 named[2005]: no IPv6 interfaces found
>Feb 20 09:49:58 ns2 named[2005]: listening on IPv4 interface lo,
>127.0.0.1#53
>Feb 20 09:49:58 ns2 named[2005]: socket.c:1183: unexpected error:
>Feb 20 09:49:58 ns2 named[2005]: setsockopt(10, SO_TIMESTAMP) failed
>Feb 20 09:49:58 ns2 named[2005]: listening on IPv4 interface eth0,
>209.58.33.71#
>53
>Feb 20 09:49:58 ns2 named[2005]: socket.c:1183: unexpected error:
>Feb 20 09:49:58 ns2 named[2005]: setsockopt(12, SO_TIMESTAMP) failed
>Feb 20 09:49:58 ns2 named[2005]: socket.c:1183: unexpected error:
>Feb 20 09:49:58 ns2 named[2005]: setsockopt(9, SO_TIMESTAMP) failed
>Feb 20 09:49:58 ns2 named[2005]: dns_master_load: db.127.0.0:1: no TTL
>specified
>Feb 20 09:49:58 ns2 named[2005]: dns_zone_load: zone
>0.0.127.IN-ADDR.ARPA/IN: da
>tabase db.127.0.0: dns_db_load failed: no ttl
>Feb 20 09:49:58 ns2 named[2005]: loading zones: no ttl
>Feb 20 09:49:58 ns2 named[2005]: exiting (due to fatal error)
>Feb 20 09:50:00 ns2 CROND[2010]: (root) CMD ( /sbin/rmmod -as)
There are several things wrong here.
First I should point out RedHat 7.1beta comes with BIND 9 as a package.
Second if you're using BIND 8 named config files and you don't have a top line which
looks like:
$TTL 86400
before your SOA record, then you will see the message about "no ttl".
Thirdly, and this is really the only kernel-related one, it appears that
named is asking for support for TIMESTAMP on the socket and it's failing.
I don't know why that is, as it looks like the TIMESTAMP socket option is supported
in 2.4 (presumably 2.2 as well).
Dave
Hi.
> I am configuring Bind 9 on Redhat 7 but unable to start the named.
> Here is my /var/log message log:
<snip named start log>
Read the documentation and you shall notice that you must set a ttl for
each zone, which also your logs state that you have not done ...
// Stefan