db.cache format for BIND 9.1.2

[kholikt]

Previously we are using the ICS version of BIND 8.2.3. We plan to upgrade to HP version of BIND 9.1.2. I have some problem with db.cache file format.

ICS Version of BIND 8.2.3. The following db.cache file is working perfectly.
. IN NS dnssec1.sinet.com.
. IN NS dnssec2.sinet.com.
. IN NS dnssec3.sinet.com.
dnssec1.sinet.com. IN A 175.21.83.11
dnssec2.sinet.com. IN A 176.13.10.226
dnssec3.sinet.com. IN A 169.21.100.11

When I tried to upgrade BIND 9.1.2. The named daemon refuse to start and give the following error message.
db.cache:1: no TTL specified; zone rejected
could not configure root hints from 'db.cache': no ttl

So I modify the db.cache file to the following format and named daemon finally started.
. IN SOA mydns.mydomain.com. root.mydns.mydomain.com. (
205 10800 3600 604800 600 )

. IN NS dnssec1.sinet.com.
. IN NS dnssec2.sinet.com.
. IN NS dnssec3.sinet.com.
dnssec1.sinet.com. IN A 175.21.83.11
dnssec2.sinet.com. IN A 176.13.10.226
dnssec3.sinet.com. IN A 169.21.100.11

However I have a new error message in the syslog.log
db.cache:1: no TTL specified; using SOA MINTTL instead
extra data in root hints 'db.cache'

For faster query I do not want to use those root DNS server and generated db.cache file.

I have browse through lot of example on the internet but it seems to be that the first format is correct. Perhaps BIND 9.1.2 has a different format. Please help.

[U.SivaKumar_2 · Accepted solution]

Hi,

You are missing explicit $TTL parameter. It should be like this.

$TTL 300

. IN SOA mydns.mydomain.com. root.mydns.mydomain.com. (
205 10800 3600 604800 600 )

. IN NS dnssec1.sinet.com.
. IN NS dnssec2.sinet.com.
. IN NS dnssec3.sinet.com.
dnssec1.sinet.com. IN A 175.21.83.11
dnssec2.sinet.com. IN A 176.13.10.226
dnssec3.sinet.com. IN A 169.21.100.11


regards,
U.SivaKumar

[harry d brown jr]

It's not an ERROR message, it's informational or a warning. But like U.SivaKumar said, it's "cured" with the $TTL directive.

live free or die
harry

[harry d brown jr]

See attachment for configuration.