refresh_callback: zone , after bind9 upgrade

Mark.Andrews at nominum.com Mark.Andrews at nominum.com
Tue Aug 7 22:08:48 UTC 2001


	A refresh_callback is the code called when a refresh query
	succeeds or fails.  A refresh query is the query made to
	see if the zone is up to dat.  The server will make three
	of these before it gives up and reschedules roughly retry
	seconds later.  The failure is that the nameserver didn't
	get a response in the expected time (timed out).

	Mark

> 
> I recently upgraded one of my slaves to bind 9.1.3. (My master is an
> old bind8 box)
> Now I receive several:
> /opt/bind9/sbin/named[646]: refresh_callback: zone
> 155.62.209.in-addr.arpa/IN: failure for 10.1.1.6#53: timed out
> 
> I have noticed tons of posts here regarding the same thing, but no
> real resolution.  It seems harmless since the zones are getting
> transfered, but I am wondering exactly what refresh_callback does and
> why it's failing.  This happens with a large number of zones (maybe
> all, I haven't been able to sift through it yet).  Eventually it also
> gets an error for maximum number of retries exceeded for
> refresh_callback as well for each zone.
> 
> Does anyone know the real problem here?  There is no firewall access
> or permission problems, since this machine formerly transfered zones
> without the error and dig axfr transfers the zone fine.
> 
> Is this something new in bind9 or an incompatibility between bind8 and
> 9?
> 
> Any help would be greately appreciated.
> Jerry
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com


More information about the bind-users mailing list