From owner-freebsd-questions Mon Nov 11 2:11:53 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 50C4137B401 for ; Mon, 11 Nov 2002 02:11:50 -0800 (PST) Received: from mta04bw.bigpond.com (mta04bw.bigpond.com [139.134.6.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5199243E6E for ; Mon, 11 Nov 2002 02:11:44 -0800 (PST) (envelope-from iain@voffice.myspinach.org) Received: from iain2.va.com.au ([144.135.24.81]) by mta04bw.bigpond.com (Netscape Messaging Server 4.15 mta04bw Jul 16 2002 22:47:55) with SMTP id H5EPNC00.EJA for ; Mon, 11 Nov 2002 20:11:36 +1000 Received: from CPE-203-45-8-24.vic.bigpond.net.au ([203.45.8.24]) by bwmam05.mailsvc.email.bigpond.com(MailRouter V3.0n 38/47091439); 11 Nov 2002 20:11:36 Received: (qmail 12561 invoked from network); 11 Nov 2002 10:11:36 -0000 Received: from unknown (HELO duro) (192.168.1.16) by 192.168.1.1 with SMTP; 11 Nov 2002 10:11:36 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Iain To: freebsd-questions@FreeBSD.ORG Subject: Re: strange problems with BIND 9.2.1 Date: Mon, 11 Nov 2002 21:11:35 +1100 User-Agent: KMail/1.4.3 References: <200211111601.40202.iain@voffice.myspinach.org> <20021111082136.GB4812@happy-idiot-talk.infracaninophi> In-Reply-To: <20021111082136.GB4812@happy-idiot-talk.infracaninophi> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200211112111.35154.iain@voffice.myspinach.org> 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 Hi, thanks for the reply, On Mon, 11 Nov 2002 07:21, Matthew Seaman wrote: > 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. There are no notify keywords in named.conf. Maybe it is sending the updat= es but they aren't being applied. It is hard for me to tell as the logging isnt working. > > > // 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: I tried adding the quotes, it makes no difference. There are no syntax er= rors reported on startup either. > 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? On startup I see the following messages: Nov 11 20:33:41 shiraz named[71623]: command channel listening on 127.0.0= =2E1#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 maste= r 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 s= pecified; using SOA MINTTL instead Nov 11 20:33:41 shiraz named[71623]: slave/named.dessertstorm.org:6: no T= TL specified; using SOA MINTTL ins tead The named.conf is as follows with ips replaced with xx: options { directory "/etc/namedb"; listen-on { xx.xx.xx.xx; }; }; // reduce log verbosity on issues outside our control logging { channel default_channel { syslog local5; severity info; }; category lame-servers { "null"; }; category "default" { "default_channel"; }; }; zone "0.0.127.in-addr.arpa" { type master; file "named.127.0.0"; }; zone "." { type hint; file "named.root"; }; zone "xx.xx.xx.in-addr.arpa" { type master; file "named.xx.xx.xx"; }; zone "xx.org.au" { type master; file "named.xx.org.au"; }; > > =09Cheers, > > =09Matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message