named stops responding on zone transfers

Federico Bockel fbockel at arnet.net.ar
Mon Apr 30 06:04:32 UTC 2001


I got lots of this when the slaves stop answering.
The thing is 200.45.0.114 its on the same vlan, switch, so there is no
network/firewall stuff in thi.
But what I see it's a large # of failed updates at the moment, what I
thought is that the master cant answer so many updated at the same time,
and at the same time this on the slaves side producing the named to
answer 1 of 10 nslookups.
That's why I limited the # of zone transfers.
Thanks

	Federico

Apr 30 02:05:07.759 general: info: refresh_callback: zone
grupocheff.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:07.759 general: info: refresh_callback: zone
slsconsultora.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:08.259 general: info: refresh_callback: zone
fripacksrl.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:08.259 general: info: refresh_callback: zone
leas.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:08.259 general: info: refresh_callback: zone
deltacom.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:08.758 general: info: refresh_callback: zone
zucregroup.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:08.759 general: info: refresh_callback: zone
fletesnet.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:08.759 general: info: refresh_callback: zone
turismoenmadryn.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:08.759 general: info: refresh_callback: zone
mehring.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:09.279 general: info: refresh_callback: zone
andana-catering.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:09.279 general: info: refresh_callback: zone
ultraguia.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:09.779 general: info: refresh_callback: zone
vialtosca.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:09.779 general: info: refresh_callback: zone
dibenedettosrl.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:09.779 general: info: refresh_callback: zone
ing-riogrande.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:10.279 general: info: refresh_callback: zone
absibariloche.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:10.279 general: info: refresh_callback: zone
caliri.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:10.279 general: info: refresh_callback: zone
puntal.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:10.279 general: info: refresh_callback: zone ucp.edu.ar/IN:
failure for 200.45.0.114#53: timed out
Apr 30 02:05:10.789 general: info: refresh_callback: zone
sooner.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:11.299 general: info: refresh_callback: zone
bigotes.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:11.299 general: info: refresh_callback: zone
lallamaquellama.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:11.809 general: info: refresh_callback: zone
vitroblock.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:12.309 general: info: refresh_callback: zone
nisi.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:12.309 general: info: refresh_callback: zone
necsus.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:12.309 general: info: refresh_callback: zone
puntalvm.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:12.819 general: info: refresh_callback: zone
estudio-scoccia.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:12.819 general: info: refresh_callback: zone
termipolsrl.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:12.819 general: info: refresh_callback: zone
sic-rma.com.ar/IN: failure for 200.45.0.114#53: timed out
Apr 30 02:05:13.319 general: info: refresh_callback: zone
contactosnorte.com.ar/IN: failure for 200.45.0.114#53: timed out

Federico Bockel
Arnet - Telecom Internet
fbockel at arnet.com.ar
 


-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
Behalf Of Jim Reid
Sent: Monday, April 30, 2001 12:41 PM
To: Federico Bockel
Cc: bind-users at isc.org
Subject: Re: named stops responding on zone transfers 


>>>>> "Federico" == Federico Bockel <fbockel at arnet.net.ar> writes:

    Federico> Im having problems when named refresh the zones, the
    Federico> service stop responding for some minutes, i have 3000+
    Federico> zones.
    Federico> Is it common that when slaves are refreshing
    Federico> zones they stop respondig for some minutes?(master
    Federico> continues responding ok)

It's not common. In fact it doesn't happen. A BIND[48] server will stop
answering queries while it loads a zone. In most circumstances, this
should be unnoticeable. It can be an issue when there are huge numbers
of resource records -- millions - or tens of thousands of zones to load.

    Federico> What can i do to solve this?

Start by showing us what's in the logs. Have you any packet traces or
debugging logs? What makes you think that the name server has stopped
processing queries because of refresh checks? Are you sure there are no
other problems, like a routing error or a broken network?

    Federico> Any idea if the transfers-in and transfers-out will help?

You've not identified the actual problem, so it's hard to see how
tinkering with the number of zone transfers will help. Or any other BIND
option for that matter. I suppose you could try all possible options in
a process of trial and error and see which, if any, make a difference.
But you'd be better off doing a root cause analysis, finding the
underlying problem and fixing it. So far, it's not even clear why the
servers are not responding for a few minutes.



More information about the bind-users mailing list