From nobody@FreeBSD.ORG  Sat Jan  1 19:58:39 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 6644815041; Sat,  1 Jan 2000 19:58:39 -0800 (PST)
Message-Id: <20000102035839.6644815041@hub.freebsd.org>
Date: Sat,  1 Jan 2000 19:58:39 -0800 (PST)
From: d-lewart@uiuc.edu
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: named 8.2.2-P5 "No default TTL set using SOA minimum instead" message
X-Send-Pr-Version: www-1.0

>Number:         15834
>Category:       misc
>Synopsis:       named 8.2.2-P5 "No default TTL set using SOA minimum instead" message
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jan  1 20:00:01 PST 2000
>Closed-Date:    Mon Jan 10 07:35:31 PST 2000
>Last-Modified:  Mon Jan 10 07:40:04 PST 2000
>Originator:     Daniel Lewart
>Release:        3.4
>Organization:
University of Illinois
>Environment:
FreeBSD lemonshark.cvm.uiuc.edu 3.4-RELEASE FreeBSD 3.4-RELEASE #0:
Mon Dec 20 06:54:39 GMT 1999
jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC  i386
>Description:
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.
>How-To-Repeat:
1) Start named
2) grep named /var/log/messages
>Fix:
Insert the following line after /etc/namedb/PROTO.localhost.rev line 7:

$TTL    3600

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: asmodai 
State-Changed-When: Mon Jan 10 07:35:31 PST 2000 
State-Changed-Why:  
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. 
>Unformatted:
