Typically you can increase the default without harm, e.g., double or x
10 if you
have a recent-vintage server with typical memory and speed, but
something might be causing the behavior that is impervious to
such a change or that needs some other kind of attention.
Such a problem might solely ste
On Wed, Mar 24, 2010 at 05:08:01PM +,
Chris Thompson wrote
a message of 46 lines which said:
> It is the length of the queue of all outstanding recursive queries.
> This depends not just on the RATE of queries coming in, but also the
> time it takes to resolve them. (If the queue fills up,
4:44.026 client: warning: client 129.88.30.5#57960: no
more recursive clients: quota reached
I have a lot of these... (two thousand unique clients blocked over the
last two weeks on my main resolver)
Is this quota global for all clients? I.e. one rogue client sending
massive amounts of recursive requ
and
> reading books, manuals and this list's archives hasn't made it entirely clear
> to me.
>
> I have the classical error logs :
>
> 17-Mar-2010 12:14:44.026 client: warning: client 129.88.30.5#57960: no more
> recursive clients: quota reached
>
> I h
ginal Message
From: Oliver Henriot
To: bind-users@lists.isc.org
Sent: Wed, March 24, 2010 10:41:28 AM
Subject: no more recursive clients: quota reached
Dear list users,
I'd like to understand a point about quotas on recursive clients quotas and
reading books, manuals and this list's
57960: no
more recursive clients: quota reached
I have a lot of these... (two thousand unique clients blocked over the
last two weeks on my main resolver)
Is this quota global for all clients? I.e. one rogue client sending
massive amounts of recursive requests would blow the quota for everyone
On Aug 28, 2009, at 8:59 AM, Dave Sparro wrote:
On Thu, Aug 27, 2009 at 12:17 PM, Niall
O'Reilly wrote:
Lisa Casey wrote:
Aug 26 12:48:56 netlink named[295]: client 207.191.185.6#60614: no
more
recursiv
e clients: quota reached
Any ideas on how I should go about solving/fixing this?
95]: client 207.191.185.6#60614: no more
> recursive clients: quota reached
>
> The client in question (206.191.185.6) is our mail server. I read that
> one should not allow recursive queries from outside of your network, but
> the mail server is within our network. Also on the mail s
On Thu, Aug 27, 2009 at 12:17 PM, Niall O'Reilly wrote:
> Lisa Casey wrote:
>
>> Aug 26 12:48:56 netlink named[295]: client 207.191.185.6#60614: no more
>> recursiv
>> e clients: quota reached
>
>> Any ideas on how I should go about solving/fixing this?
>
> I'ld suggest you check your connec
Lisa Casey wrote:
Aug 26 12:48:56 netlink named[295]: client 207.191.185.6#60614: no more recursiv
e clients: quota reached
Any ideas on how I should go about solving/fixing this?
I'ld suggest you check your connectivity and routing.
We see this behaviour occasionally, but
At Wed, 26 Aug 2009 13:37:09 -0400,
"Lisa Casey" wrote:
> The lins recursive clients: 564/1000 bothers me, did my change to
> /etc/named.conf not get oicked up? It appears that the max recursive
> clients is still at bind's default of 1000.
True. It's also true that
recursive-clients 5000
Hi,
I'm not really sure what to do about this. I'm running Bind 9 on FreeBSD.
Suddenly this morning I began noticing the following in /var/log/messages:
Aug 26 12:48:56 netlink named[295]: client 207.191.185.6#60614: no more recursiv
e clients: quota reached
Aug 26 12:48:56 netlink named[295]: c
12 matches
Mail list logo
