|Checking the logs I found this:
Nov 20 05:34:01 ducky named: starting. named 8.2.2-P5
Sat Nov 20 05:07:59 NZDT 1999
Nov 20 05:34:02 ducky named: hint zone "" (IN) loaded
Nov 20 05:34:02 ducky named: Zone "0.0.127.IN-ADDR.ARPA"
(file localhost.rev): No default TTL set using SOA
Nov 20 05:34:02 ducky named: master zone
"0.0.127.IN-ADDR.ARPA" (IN) loaded (serial 199907090)
You can see that the correct version of named (8.2.2-P5) is running and the
date it was compiled (Sat Nov 20 05:07:59 NZDT 1999).
The messages which refer to a lack of a default TTL can be safely ignored. TTL =
time to live. It dictates how long a server can cache information about your
box. The message in question is named merely telling you politely that your
zone files don't contain a default TTL. You can specify the default TTL like this:
Put that at the top of each of your zone files and those messages will go away.
This value will be used for each host for which a TTL value is not explicitly
assigned. In the above case, the default TTL is 4 days as recommended in RFC 1537 This will apply to each
host within the zone.
Custom TTL values can be assigned to individual hosts. This is done like this:
1 3600 IN PTR localhost.yourdomain.org.
For more information, I suggest you buy a copy of DNS
and Bind. It's a very useful book when you're doing anything with a DNS server.
That's how I found how what this message was all about. See p189 for an
explanation of how you can use TTL to your advantage when moving or renaming boxes.