refresh_callback: zone , after setting up new bind9 slave server
Barry Margolin
barmar at genuity.net
Fri Mar 15 22:34:12 UTC 2002
In article <a6trpb$ier at pub3.rc.vix.com>,
Brett A. Hansen <brett at annis.com> wrote:
>Hello All,
>
>I have spent a great deal of time searching the news groups with
>groups.google.com trying to find a solution to my current problem. I have
>tried just about everything that has been discussed, and I'm still having an
>issue with my Bind 9.1.3-4 package from Red Hat. I am running a Red Hat 7.2
>system with all the updates.
>
>Our current Master NAMED server is running Bind 8.2.3, I have added one more
>server that I wish to work as a slave (The Bind 9.1.3 Server). One server
>is located in Michigan, while the other is located in D.C. I have opened
>both firewalls at each end to allow ALL traffic on EVERY port to communicate
>in BOTH directions. I can remove all the slave files from the slave server,
>restart bind, and all my zones will transfer. Shortly there-after I will
>start to get 'refresh_callback: zone' errors, and then eventually the zones
>will no longer respond.
>
>>>refresh_callback: zone homey.com/IN: failure for XXX.XXX.47.158#53: timed
>out
Are you allowing both TCP and UDP through the firewalls? If the zones
transferred, you must be allowing TCP, but the periodic SOA queries use
UDP.
--
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
More information about the bind-users
mailing list