[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: BIND stops resolving hostnames
Fridtjof Busse wrote:
> 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
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.