From owner-freebsd-questions Mon Nov 11 2:57:36 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0040037B401 for ; Mon, 11 Nov 2002 02:57:34 -0800 (PST) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.69.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8750F43E8A for ; Mon, 11 Nov 2002 02:57:33 -0800 (PST) (envelope-from m.seaman@infracaninophile.co.uk) Received: from happy-idiot-talk.infracaninophile.co.uk (localhost [IPv6:::1]) by smtp.infracaninophile.co.uk (8.12.6/8.12.6) with ESMTP id gABAvV60006129 for ; Mon, 11 Nov 2002 10:57:31 GMT (envelope-from matthew@happy-idiot-talk.infracaninophile.co.uk) Received: (from matthew@localhost) by happy-idiot-talk.infracaninophile.co.uk (8.12.6/8.12.6/Submit) id gABAvQ9K006124 for freebsd-questions@FreeBSD.ORG; Mon, 11 Nov 2002 10:57:26 GMT Date: Mon, 11 Nov 2002 10:57:26 +0000 From: Matthew Seaman To: freebsd-questions@FreeBSD.ORG Subject: Re: strange problems with BIND 9.2.1 Message-ID: <20021111105726.GA5959@happy-idiot-talk.infracaninophi> Mail-Followup-To: Matthew Seaman , freebsd-questions@FreeBSD.ORG References: <200211111601.40202.iain@voffice.myspinach.org> <20021111082136.GB4812@happy-idiot-talk.infracaninophi> <200211112111.35154.iain@voffice.myspinach.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200211112111.35154.iain@voffice.myspinach.org> User-Agent: Mutt/1.5.1i X-Spam-Status: No, hits=-2.2 required=5.0 tests=IN_REP_TO,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT, USER_AGENT_MUTT version=2.43 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Nov 11, 2002 at 09:11:35PM +1100, Iain wrote: > On startup I see the following messages: > > Nov 11 20:33:41 shiraz named[71623]: command channel listening on 127.0.0.1#953 > Nov 11 20:33:41 shiraz named[71623]: command channel listening on ::1#953 > Nov 11 20:33:41 shiraz named[71623]: dns_master_load: named.syd.va.com.au:14: syd.va.com.au: CNAME and othe > r data > Nov 11 20:33:41 shiraz named[71623]: zone syd.va.com.au/IN: loading master file named.syd.va.com.au: CNAME > and other data > Nov 11 20:33:41 shiraz named[71623]: slave/named.culture2.org:6: no TTL specified; using SOA MINTTL instead > Nov 11 20:33:41 shiraz named[71623]: slave/named.dessertstorm.org:6: no TTL specified; using SOA MINTTL ins > tead Ok. The named.conf looks fine, if fairly minimal. I think that the problem is the errors in your zone files that named is complaining about. Bind 9 is rather stricter about several questionable constructs. The "CNAME and other data" thing is a case in point --- you can't mix CNAME's and other RR types for the same RRset: ; Illegal... foo IN CNAME bar IN MX blurfl You shouldn't even have multiple CNAME's in the same RRset: ; Illegal... foo IN CNAME foo1 IN CNAME foo2 although you used to be able to persuade Bind 8 to accept that given the correct options {}; statement. The "no TTL specified; using SOA MINTTL instead" thing you're seeing on those slave zones is just a warning and shouldn't prevent your server working. If the master for those zones is running Bind 8.2 or higher, you might prevail on the admin to add a reasonable default TTL at the top of the file: $TTL 7200 ; Default 3h TTL on RRs Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message