A common issue is the secondary not being allowed to query the master for the SOA of the zone. Ensure the master has an allow-query that includes the secondary. On Jan 25, 2013 6:06 AM, "Jan-Piet Mens" <jpmens....@gmail.com> wrote:
> Hello, > > I'm seeing quite a number of messages like > > xfer-out: debug 3: client 192.168.1.2#54688 (example.com): zone > transfer setup failed > > BIND 9.9.2P1 here, configured with: > > request-ixfr no; > transfer-format many-answers; > transfers-in 100; > transfers-per-ns 100; > max-transfer-time-in 60; > > BIND has a lot of zones to transfer; does this have something to do with > too many TCP connections? > > FWIW, BIND is running on Centos 6.3 in an OpenVZ container. > > Regards, > > -JP > _______________________________________________ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to > unsubscribe from this list > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users >
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
