No default TTL set using SOA minimum instead

[Cricket Liu]

> Why does bind 8.2 report this in the log when loading a zone, and how can
I
> fix the zonefile to shut it up?
>
> Jun  5 22:19:28 voyager named[3401]: Zone "huh-huh-huh.dk" (file
> named.huh-huh-huh.dk.hosts): No default TTL set using SOA minimum
> instead

That's the new RFC 2308 TTL semantics at work.  From 8.2 on, you can set the
(positive) TTL and the negative caching TTL separately, by using the new
$TTL directive (for the positive TTL) and the last RDATA field in the SOA
record (for the negative TTL).  But if you leave out the $TTL directive,
BIND 8.2 assumes you're still using the old system, and interprets the last
SOA RDATA field as both TTLs.

cricket