Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Nov 2002 21:11:35 +1100
From:      Iain <iain@voffice.myspinach.org>
To:        freebsd-questions@FreeBSD.ORG
Subject:   Re: strange problems with BIND 9.2.1
Message-ID:  <200211112111.35154.iain@voffice.myspinach.org>
In-Reply-To: <20021111082136.GB4812@happy-idiot-talk.infracaninophi>
References:  <200211111601.40202.iain@voffice.myspinach.org> <20021111082136.GB4812@happy-idiot-talk.infracaninophi>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211112111.35154.iain>