Q on clients-per-query, max-clients-per-query

[Fr34k]

Hello,

# The ARM says: #
clients-per-query, max-clients-per-query
These set the initial value (minimum) and maximum number of recursive 
simultaneous clients for any given query (<qname,qtype,qclass>) that the server 
will accept before dropping additional clients. named will attempt to self tune 
this value and changes will be logged.  The default values are 10 and 100.
If clients-per-query is set to zero, then there is no limit on the number of 
clients per query and no queries will be dropped.  If max-clients-per-query is 
set to zero, then there is no upper bound other than imposed by 
recursive-clients.


# Consider that I have: #
clients-per-query 10 ; max-clients-per-query 20 ;


# What I think this means in hypothetical situations: #
1.  If I have 100 customer Windows machines requesting A record(s) for 
non-responsive-domain.com, then my caching server will only recurs the first 20 
of such requests and drop the other 80.  Is this correct, or what is the likely 
process?

2.  If I have 100 customer Windows machines requesting A record(s) for 
very-slow-to-respond.com, then my caching server will only recurs  the first 20 
of such requests and drop the other 80.  Is this correct, or what is the likely 
process?

Let's say the name servers authoritative for this domain finally respond, then 
my bind server will respond to the 20 queries.
Is this correct, or what is the likely process?

Now that I have the A record for www.very-slow-to-respond.com in cache (say TTL 
is 24h) and it is likely that the 80 unsatisfied customer Windows machines will 
make another query attempt and, because I have this cached, finally get a 
response.
Is this correct, or what is the likely process?

It won't hurt my feeling if someone rather provide a better example that may 
demonstrate how these settings work.

Thank you.