refresh: failure trying master / zone transfer failure

[Kevin Darcy]

BIND has the ability (the "allow-transfer" clause) to restrict zone
transfers, but then you'd get different log messages. This looks more
like a networking/firewall problem of some sort. Make sure that 53/TCP is
open between the boxes.


- Kevin

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