From owner-freebsd-questions Tue Feb 1 1:31: 8 2000 Delivered-To: freebsd-questions@freebsd.org Received: from rivendell.mel.vet.com.au (rivendell.mel.vet.com.au [203.103.154.61]) by builder.freebsd.org (Postfix) with ESMTP id 7F1073D86 for ; Tue, 1 Feb 2000 01:31:04 -0800 (PST) Received: (from lodea@localhost) by rivendell.mel.vet.com.au (8.9.3/8.9.3) id TAA04521; Tue, 1 Feb 2000 19:21:30 +1100 (EST) Date: Tue, 1 Feb 2000 19:21:30 +1100 From: "Lachlan O'Dea" To: Grandpa Walrus Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Question about named Message-ID: <20000201192129.F3994@vet.com.au> Mail-Followup-To: Grandpa Walrus , freebsd-questions@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.2i In-Reply-To: ; from root@web-walrus.com on Mon, Jan 31, 2000 at 07:51:06PM -0600 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 31, 2000 at 07:51:06PM -0600, Grandpa Walrus wrote: > I'm getting a "No default TTL set using SOA minimum instead" message when > named tries to parse this file: [snip] > Can anybody point me to a resource that will explain this message? > Any help would be greatly appreciated RFC2308 has the gory details on this if you're interested. Basically the minimum TTL for records is no longer set by the SOA, but by the $TTL directive, eg: $TTL 86400 Adding $TTL to your master file should get rid of the message. It's not a big deal though - Bind is just telling you it couldn't find $TTL, so it's using the SOA value. -- Lachlan O'Dea Computer Associates Pty Ltd Webmaster Vet - Anti-Virus Software http://www.vet.com.au/ "Try not. Do. Or do not. There is no try." - Yoda, Jedi Master To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message