no more recursive clients: quota reached

Mark Andrews Mark_Andrews at
Tue Sep 11 22:56:29 UTC 2007

> You could always turn on query logging. That would log each query that is
> being made and show you who is spiking your queries. If you are looking for
> a monitoring tool, Raffy Marty wrote an interesting tool that can hook in to
> DNS logs called Afterglow. It's been awhile since I've played with the tool,
> but it would probably do what you are looking for.
>  Raffy is a good guy. I'm sure if you
> needed any help setting it up he'd be more than happy to offer some
> pointers.

	When it is happening 'rndc recursing' will show what is in the

	Looking at who is making what queries will not see the cause.
	You need to see what queries are taking a long time to resolve
	as most queries on sit in the list for a few milliseconds.

	Also if you are not running BIND 9.4 I would upgrade to it
	as it changes how the list is managed.

> On 9/11/07, Niall O'Reilly <Niall.oReilly at> wrote:
> >
> > "no more recursive clients: quota reached".  In the past, we've
> > been able to match these to connectivity problems for an outlying
> > site with its own local name servers which has become isolated
> > from the "greater Internet".
> > A recent incident doesn't fit this explanation.  I'm wondering
> > how best to determine whether the configured quota needs to be
> > adjusted.
> >
> > If anyone has a better idea than periodically dumping stats
> > and tracking the value tagged 'recursion' there, I'ld appreciate
> > the hint.
> >
> > I've looked (perhaps not hard enough) for an MRTG-compatible
> > script to do what's needed, and not found one.  If anyone is
> > interested in the one I expect to write soon, I'll be glad to
> > share it.
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at

More information about the bind-users mailing list