BIND 9 tcp-client quotas
Richard Caissie (EUD)
Richard.Caissie at am1.ericsson.se
Fri Sep 13 15:28:35 UTC 2002
> The nameserver stops accepting future connections until the current
> ones complete / are timed out. Note the kernel may complete the
> handshake up to the listen queue length.
If I have 10 active AXFR clients going with a tcp-clients setting of 10, should
I be able to do a dig as follows and get an answer?
dig +time=999 +tcp localhost
The named.run file shows that the TCP quota is reached, but BIND 9 still answers the
From: Mark.Andrews at isc.org [mailto:Mark.Andrews at isc.org]
Sent: Thursday, September 12, 2002 7:49 PM
To: Richard Caissie (EUD)
Cc: bind9-users at isc.org; bind9-workers at isc.org
Subject: Re: BIND 9 tcp-client quotas
> The ARM states that tcp-clients sets "The maximum number of simultaneous clie
> nt TCP connections that the server will accept."
> When I set this to 1 with BIND 9.2.1/Solaris 8, I am able to do two and more
> simultaneous AXFRs. Is there something wrong with the server or did I read th
> ARM the wrong way?
> After the second AXFR the named.run file shows:
> Sep 12 15:58:54.043 client 127.0.0.1#33478: no more TCP clients: quota reache
> Sep 12 15:58:54.045 client 127.0.0.1#33478: transfer of '184.108.40.206.5.e164.arpa/
> IN': AXFR
The nameserver stops accepting future connections until the current
ones complete / are timed out. Note the kernel may complete the
handshake up to the listen queue length.
> many thanks,
> Richard Caissie
> DNS & DHCP Development Unit
> 959 Concord Street
> Framingham, MA 01701
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews at isc.org
More information about the bind-workers