Bug 15834

Summary: named 8.2.2-P5 "No default TTL set using SOA minimum instead" message
Product: Base System Reporter: d-lewart <d-lewart>
Component: miscAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description d-lewart 2000-01-02 04:00:01 UTC 
After starting named 8.2.2-P5, this appears in /var/log/messages:

  Dec 27 19:31:26 lemonshark named[6000]: Zone "0.0.127.IN-ADDR.ARPA"
  (file localhost.rev): No default TTL set using SOA minimum instead

This is a new named quirk, which is easily fixed.

Fix: 

Insert the following line after /etc/namedb/PROTO.localhost.rev line 7:

$TTL    3600
How-To-Repeat: 1) Start named
2) grep named /var/log/messages
Comment 1 Jeroen Ruigrok van der Werven freebsd_committer freebsd_triage 2000-01-10 15:35:31 UTC 
State Changed
From-To: open->closed

This was fixed by Peter Wemm in rev 1.6 and 1.4.2.2 of PROTO.localhost.rev. 
To quote Peter: "RFC2038 and bind 8.2.2 have a slight variation of  
interpretation of the SOA 'minimum' field. Now it's necessary to define 
$TTL seperately to shut it up." 

So one needs to add a $TTL abive the @ in the zone file to get rid of 
the `no default TTL set, using SOA minimum instead' messages.