refresh: failure, after setting up new bind bind-9.2.0 server

[Barry Margolin]

In article <a7o9i5$mi4 at pub3.rc.vix.com>,
Brett A. Hansen <brett at annis.com> wrote:
>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.2.0 Server).  One master
>server is located in Washington State, while the slave other is located in
>Washington 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: failure trying
>master 216.168.47.158#53: timed out' errors, and then eventually the zones
>will no longer respond.

Have you tried putting a sniffer on the LAN to see the DNS traffic between
the master and slave?

-- 
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.