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 wrote in message news:<ais4uv$dlc7$1 at isrv4.isc.org>...
> > > 
> > > 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
> First sorry to so many questions below,
> 
> I)but the result did not seem to be any error.right?
> and no connection error between master and slave.
> here is the result of 'Err/TO getting serial# for
> "201.96.202.in-addr.arpa"',
> nns.sta.net.cn% dig +norec 201.96.202.in-addr.arpa @ns.sta.net.cn SOA

	I said "cut and paste".  You did not cut and paste.  I'm
	sure you don't have ns.sta.net.cn in named.conf.  You have
	a IP address in named.conf.
	
 
> ; <<>> DiG 8.1 <<>> +norec 201.96.202.in-addr.arpa @ns.sta.net.cn SOA 
> ; (1 server found)
> ;; res options: init defnam dnsrch
> ;; got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
> ;; flags: qr aa ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
> ;; QUERY SECTION:
> ;;      201.96.202.in-addr.arpa, type = SOA, class = IN
> 
> ;; ANSWER SECTION:
> 201.96.202.in-addr.arpa.  3D IN SOA  ns.sta.net.cn.
> root.ns.sta.net.cn. (
>                                         2002080505      ; serial
>                                         3H              ; refresh
>                                         30M             ; retry
>                                         5w6d16h         ; expiry
>                                         3D )            ; minimum
> 
> 
> ;; AUTHORITY SECTION:
> 201.96.202.in-addr.arpa.  3D IN NS  ns.sta.net.cn.
> 201.96.202.in-addr.arpa.  3D IN NS  nns.sta.net.cn.
> 
> ;; ADDITIONAL SECTION:
> ns.sta.net.cn.          3D IN A         202.96.199.133
> nns.sta.net.cn.         3D IN A         202.96.199.132
> 
> ;; Total query time: 3 msec
> ;; FROM: nns.sta.net.cn to SERVER: ns.sta.net.cn  202.96.199.133
> ;; WHEN: Thu Aug  8 16:06:36 2002
> ;; MSG SIZE  sent: 41  rcvd: 159
> 
> and zone file is here,
> $TTL    259200;
> @       IN      SOA     ns.sta.net.cn.  root.ns.sta.net.cn. (
>         2002080505      ; Serial by kitty
>         10800           ; Refresh
>         1800            ; Retry
>         3600000         ; Expire
>         259200  )       ; Minimum
>         IN      NS      ns.sta.net.cn.
>         IN      NS      nns.sta.net.cn.
> 
> II)BTW,I've correct some old zone files which have space instead of
> table
> like'@<space><space><space><space>IN'to'@<table>IN'
> Is it necessory in bind8.3.3? earlier bind version seem to not that
> strict!?

	No. BIND 8 doesn't care how the white space is made up.
> 
> III)and the CPU useage is more high than before after I upgrade to
> bind8.3.3 on solaris 2.6
> 
> I found more and more logs like,
> ....
> sysquery: query(NS.cmmail.com) All possible A RR's lame
> ....
> Why?
> Does that configure of logging 'category lame-servers { null; };'
> can not prevent such logs?
> how can i set the named.conf in bind8.3.3 to prevent such logs??
> or should i contact the zone owner to report their zone err?

	I would report the error to the zone owner.
> 
> 
> thank you
> 
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org