too many zone transfers after a reconfig

[torben fjerdingstad]

I wrote:
> > Why is my slave server transferring the 'dk' zone very often?

On Thu, Aug 03, 2000 at 04:20:56AM +1000, Mark.Andrews at nominum.com wrote:
> 
> 	I suggest that you look for other messages from named indicating
> 	error is children / grandchildren of dk.  I suspect that dk is
> 	being reloaded because other zones have expired and dk is being
> 	reloaded to replace glue that would might have been occulted by
> 	the child zone.
> 
> 	Mark

I have 6 expired slave .dk subzones.

I don't get the point of reloading the zone file over and over
again, when the serial number has not changed? Can an expired
zone poison the glue, or?

That problem is almost killing ns-soa.darenet.dk. Yesterday I
reloaded 2 zones with ndc reload <zone>. A little later, I
did a total reload with ndc reload. As it does not respond
to queries while loading the 40Mb zone file, it hurts badly.
Now, it's bind-8.2.2-P7.

Dec 28 18:57:27 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 18:59:08 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 19:00:49 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 19:03:54 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 19:22:11 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 19:28:59 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 19:32:32 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 19:49:04 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 19:50:49 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 19:52:32 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 19:54:13 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 19:55:55 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 19:57:36 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 19:59:18 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 20:01:00 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 20:02:41 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 20:04:23 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 20:06:04 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 20:07:46 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 20:09:28 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 20:11:10 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 20:12:53 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)
Dec 28 20:14:36 ns named[16296]: slave zone "dk" (IN) loaded (serial 2000122801)


> > I run a slave server (ns-soa.darenet.dk) for the country
> > toplevel zone 'dk' with  bind-8.2.2-P5.
> > The zone file is over 30Mb large.
> > 
> > While the transfor goes on, named is non-responsive to
> > queries, which makes this a big problem. On Aug 2, I
> > did an 'ndc reconfig' twice, at 11:02 and once again
> > a few minutes later.
> > 
> > It seems to settle at night.
> > 
> > /etc/namedb # grep '"dk"' /var/adm/messages
> > Aug  1 11:57:13 ns named[14946]: slave zone "dk" (IN) loaded (serial 2000080
> > 100)
> > Aug  1 13:17:56 ns named[14946]: slave zone "dk" (IN) loaded (serial 2000080
> > 100)
> 	[snip]

-- 
Med venlig hilsen / Regards 
Netdriftgruppen / Network Management Group
UNI-C          

Tlf./Phone   +45 35 87 89 41        Mail:  UNI-C                                
Fax.         +45 35 87 89 90               Bygning 304
E-mail: torben.fjerdingstad at uni-c.dk       DK-2800 Lyngby