refresh: failure trying master / zone transfer failure

[Barry Margolin]

In article <a2n3i2$pnh at pub3.rc.vix.com>,
deviatethenorm <burn at variate.net> wrote:
>
>i rebuilt NS3, its acting as a slave to NS1, so i went ahead and
>dumped the conf files (named.conf, named.boot) from NS2 to NS3,
>however, BIND starts up fine but zone transfers will not happen from
>ns1 to ns3:
>
>ns3 logs:
>-----------------------
>Jan 23 07:37:25 ns3 named[1571]: zone fhlbtradedesk1.com/IN: refresh:
>failure trying master 10.13.150.188#53: timed out
>Jan 23 07:37:26 ns3 named[1571]: zone fhlb-of.com/IN: refresh: failure
>trying master 10.13.150.188#53: timed out
>Jan 23 07:37:26 ns3 named[1571]: zone fhlbbonddesk.com/IN: refresh:
>failure trying master 10.13.150.188#53: timed out
>Jan 23 07:37:26 ns3 named[1571]: zone fhlbof.com/IN: refresh: failure
>trying master 10.13.150.188#53: timed out
>Jan 23 07:37:26 ns3 named[1571]: zone fhlbtradedesk.com/IN: refresh:
>failure trying master 10.13.150.188#53: timed out
>Jan 23 07:37:26 ns3 named[1571]: zone 0.242.64.IN-ADDR.ARPA/IN:
>refresh: failure trying master 10.13.150.188#53: timed out
>
>the logs on ns1 just say that it has sent notifies out and if i delete
>a zone on ns2 and restart bind, then the zone gets retransfered no
>problem, does bind use some kind of known hosts like ssh? im stumped,
>any help is appreciated.

Looks like some kind of communication problem between ns3 and ns1.  If you
have any kind of packet filtering on ns1 or ns3, or in between them, it's
possible that it could be the problem.

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