Why is my BIND 9.2.0 name server slow at resolving queries?
Answered Fri, 31 May 2002> I recently upgraded several Bind8.2.3 resolver-only servers to 9.2.0.
> Within one hour I was receiving the below error on all -
>
> no more recursive clients: quota reached
>
> I added the recursive-client option and increased it to 12000 which
> corrected the problem, shortly thereafter the servers stopped answering
> queries or would take a rather long time to answer. I logged onto one of
> the servers and tried some queries and received the following error -
>
> <<>> DiG 9.2.0 <<>> "any-domain-I-used"
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
>
> I downgraded back to 8.2.3 and all works fine. Is there something I need to
> add for a high-volume resolver with bind9.2.0 ? I ruled out connectivity
> problems since it happened to geographically separated servers.
It's tough to say. I would have looked at other resource constraints while
the name server was slow to try to determine what had happened. But
the top-end performance of a BIND 9 name server is not as high as that
of a BIND 8 name server, so maybe yours is one of those installations
that still needs BIND 8.
Still, I'd use 8.2.5 or 8.3.1, not 8.2.3.
cricket