From: dek_ml@konerding.com
To: Ansari <mike@khi.sdnpk.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Running Bind 9 on Redhat 7
Date: Mon, 19 Feb 2001 08:27:14 -0800 [thread overview]
Message-ID: <200102191627.f1JGRE621842@konerding.com> (raw)
In-Reply-To: Your message of "Mon, 19 Feb 2001 20:00:48 +0500." <3A913520.3011C7D6@khi.sdnpk.org>
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
next prev parent reply other threads:[~2001-02-19 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-19 15:00 Running Bind 9 on Redhat 7 Ansari
2001-02-19 16:13 ` Paul Jakma
2001-02-19 16:27 ` dek_ml [this message]
2001-02-19 21:22 ` [OT] " Stefan Smietanowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200102191627.f1JGRE621842@konerding.com \
--to=dek_ml@konerding.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@khi.sdnpk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox