BIND 9 and TTLs

[Mark.Andrews at nominum.com]

> Hi Kevin:
> 
> Kevin Darcy wrote in message <39C81160.38E379DB at daimlerchrysler.com>...
> >The infamous "Brian" wrote:
> >> If I place the <TTL> value in the RRs, no joy!
> 
> >_DNS_and_BIND_ 2nd Edition is somewhat outdated. RFC 2308
> >clarified that the last field of the SOA record is the
> >Negative Caching TTL, not the default or minimum TTL.
> 
> OK - good.
> 
> >That's why BIND 9 requires the presence of a $TTL directive
> >(also specified in RFC 2308), or an explicit TTL on the *first*
> >record in the zone file; otherwise it doesn't know what TTL to
> >use for the record(s). See doc/misc/migration, Section 2.1.
> 
> 
> Read the migration DOC - that's what led to my attempts to place TTL
> directives in the RRs. I even tried putting it in every RR in case that was
> my problem.
> 
> Here is a copy of my "0.0.127.in-addr.arpa" zone;
> 
> ---<clip>---
> $TTL  1D
> @             IN    SOA    bozo    subdude.post.com.  (
>                              10       ; Serial
>                              8H       ; Refresh
>                              1H       ; Retry
>                              1W       ; Expire
>                              1D       ; Minimum
>                              )
> 
> @           IN    NS         bozo
>             IN    NS         bungo
> 
> 1           IN    PTR        localhost
> 
> ---<clip>---
> 
> The above works.
> 
> ---<clip>---

	The docs say *first* record. The SOA record is the first record
	in this file and it does not have a explict ttl hence the error
	message.

> @             IN    SOA    bozo    subdude.post.com.  (
>                              10       ; Serial
>                              8H       ; Refresh
>                              1H       ; Retry
>                              1W       ; Expire
>                              1D       ; Minimum
>                              )
> 
> @      1D     IN    NS       bozo
>        1D     IN    NS       bungo
> 
> 1      1D     IN    PTR      localhost
> 
> ---<clip>---
> 
> The above doesn't work.
> 
> Here is the /var/log/syslog messages;
> 
> ---<clip>---
> Sep 19 18:53:24 bozo named[72]: dns_master_load: named.127.0.0:1:
> no TTL specified
> Sep 19 18:53:25 bozo named[72]: dns_zone_load: zone
> 0.0.127.in-addr.arpa/IN: database named.127.0.0: dns_db_load failed:
> no ttl
> ---<clip>---
> 
> Is this perhaps a "Linux" thing?
> 
> Best regards,
> 
> Brian
> 
> 
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com