Zone transfer deferred due to quota

Mark Andrews Mark_Andrews at isc.org
Tue Sep 5 00:57:17 UTC 2006


> Hi !
> 
> I have set this in SLAVE:
> 
>        /*
>           Only used by slave zones.
>           transfer-in determines the number of concurrent inbound zone
> transfers.
>           Default is 10. This statement may only be defined in a
> global options clause.
>         */
>         transfers-in 100;
> 
> 
> 
> and this in MASTER:
> 
>         /*
>           Only used by master zones.
>           transfers-out determines the number of concurrent outbound
> zone transfers.
>           Default is 10. Zone transfer requests in excess of this
> limit will be REFUSED.
>           This statement may only be defined in a global options clause.
>         */
>         transfers-out 100;
> 
> 
> but I have always this problem:
> 
> Sep  4 17:13:24 ns2 named[9473]: zone
> 0.168.192.in-addr.arpa/IN/external-in: refresh: retry limit for master
> 192.168.0.2#53 exceeded (source 192.168.0.1#0)
> Sep  4 17:13:24 ns2 named[9473]: zone
> 0.168.192.in-addr.arpa/IN/external-in: zone transfer deferred due to
> quota
> 
> 
> Can You help me?
> 
> Thanks


	There really is no point in having lots of transfers happening
	in parrallel.  All it does is stress the master server.  It
	doesn't speed up transfers as the deferred transfers will
	be started when the transfers that caused the deferral complete.

	What you need to workout is why you are not getting responses
	to the SOA queries over UDP.

	Mark
--
ISC Training!  October 16-20, 2006, in the San Francisco Bay Area,
covering topics from DNS to DHCP.  Email training at isc.org.
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org



More information about the bind-users mailing list