Why I got more and more such information after I upgrade bind? and high CPU useage?
Mark_Andrews at isc.org
Mark_Andrews at isc.org
Wed Aug 7 21:52:26 UTC 2002
>
> Pete Ehlke <pde at ehlke.net> wrote in message news:<aim5on$b6uh$1 at isrv4.isc.org
> >...
> > On Mon, Aug 05, 2002 at 03:17:17AM -0700, David Xiao wrote:
> > >
> > > Does bind8.3.3's syntax more stricter than old version?
> >
> > Stricter than some older versions, yes.
> >
> > > because I found that my slave can not get some zones' serial
> > > the log like,
> > > ...
> > > Err/TO getting serial# for "abc.com"
> > > ...
> > There will be other messages surrounding this one that are more
> > descriptive. What do they say?
> >
> > -Pete
>
> when I restart master the log on slave have the log like,
> ......
> Err/TO getting serial# for c.b.a.in-addr.arpa
> .......
> NOTIFY(SOA) for zone already xferring (c.b.a.in-addr.arpa)
> .....
>
Err/TO means that the refresh query failed to get a response
or that response indicated that the master was not authoritative
for the zone.
The server is doing the following.
dig +norec zone @master soa
You should get only the SOA record for the zone in the
answer section. "aa" should be set in flags.
If you don't then you have connectivity problems, the master
failed to load the zone, the master is not configured for
the zone or you have the wrong IP address.
I suggest cutting and pasting the relevent parts from
named.conf so you don't "correct" a typo by doing it by
hand.
Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews at isc.org
More information about the bind-users
mailing list