From owner-freebsd-questions Mon Nov 11 0:21:52 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 E3BF037B401 for ; Mon, 11 Nov 2002 00:21:50 -0800 (PST) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.69.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84CE643E4A for ; Mon, 11 Nov 2002 00:21:49 -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 gAB8Lg60005224 for ; Mon, 11 Nov 2002 08:21:42 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 gAB8Ladn005223 for freebsd-questions@FreeBSD.ORG; Mon, 11 Nov 2002 08:21:36 GMT Date: Mon, 11 Nov 2002 08:21:36 +0000 From: Matthew Seaman To: freebsd-questions@FreeBSD.ORG Subject: Re: strange problems with BIND 9.2.1 Message-ID: <20021111082136.GB4812@happy-idiot-talk.infracaninophi> Mail-Followup-To: Matthew Seaman , freebsd-questions@FreeBSD.ORG References: <200211111601.40202.iain@voffice.myspinach.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200211111601.40202.iain@voffice.myspinach.org> User-Agent: Mutt/1.5.1i X-Spam-Status: No, hits=-3.0 required=5.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,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 04:01:40PM +1100, Iain wrote: > The main problem is that NOTIFY messages aren't being sent from the master to > the slaves. However I am also having trouble modifying the logging. You normally have to put some effort into preventing named sending notifications. Usually if you let named default (ie. don't use any sort of 'notify' keywords in named.conf) then named will send notifications of any zone update to all of the servers given in NS records for the zone. > // reduce log verbosity on issues outside our control > logging { > channel default_channel { > syslog local5; > severity info; > }; > category lame-servers { null; }; > category "default" { "default_channel"; }; > }; About the only minor nit I can see in that is a slight lack of quote marks, compared to what the documentation says: category lame-servers { "null"; }; but I wouldn't expect that to make a great difference. You will still see the named startup messages logged to /var/log/messages, as your customised logging only kicks in after the whole configuration file has been parsed. See the documentation in, for instance: file:///usr/local/share/doc/bind9/arm/Bv9ARM.ch06.html#AEN1566 > I can't think why the master server is not sending notify messages. The > secondaries are defined in the zone files and are setup as slaves. There's nothing much wrong in what you've posted, and named should be working in the way you intend. What does named log on startup? Any chance of posting the whole named.conf file? 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