Re: BIND stops resolving hostnames

[Fridtjof Busse <misc-list@fbunet.de>]

* Mike Lewinski <mike@rockynet.com>:
> > But when BIND stops resolving hostnames again, all I get in the
> > logfile is an entry about the "IN A" query itself, but no error at
> > all (although the query doesn't resolve).
> > After a SIGHUP everything works fine again.
> > Is my log-level not high enough?
>
> We've also had an issue with BIND lately. In our case, logging did
> the trick, and we tracked back the culprit to a machine which was
> doing massive amounts of reverse lookups (processing firewall logs of
> all the virus crap). Disabling the reverses on that machine have
> resolved this issue for us (so far anyway). The log messages that
> tipped us off looked like this:
>
> Aug 29 06:21:03.457 client: client 192.168.254.13#1785: no more
> recursive clients: quota reached
>
> Note that BIND seemed to stop some time after these messages
> appeared, so you may need to get creative w/ grep or just pore over
> the log history rather than look at the very last lines.

Nope, nothing like this here. My network is rather small, 
reverse-lookups only occur during mailtransfer etc.
I less'ed the entire log, nothing but queries and notifications about 
zone-updates.
BIND simply stops resolving hostnames: Most resolve fine, but some 
don't. I'm not authoritative for them. 
Not reproducible in any way, occurs infrequently.
Any idea what might cause this (usually I use djbdns)?

-- 
Fridtjof Busse
There's a way out of any cage.
		-- Captain Christopher Pike, "The Menagerie" ("The Cage"),
		   stardate unknown.