BIND query queues/timeouts
Barry Margolin
barmar at alum.mit.edu
Tue Jan 1 07:19:42 UTC 2008
In article <flbekm$1n73$1 at sf1.isc.org>,
Tim Maestas <tim at dnsconsultants.com> wrote:
> We're running bind 9.3.4 (also see the issue described below on 9.4.2 as
> well) on a dual CPU SUN V210 running Solaris 9. Every so often we are
> seeing a spike in query traffic to the main IP of the servers that clients
> point to for recursive nameservice. After this, BIND appears to be unable
> to answer new queries, or is answering them very slowly. CPU usage goes
> up, but there are still idle cycles available. During this period, when
> BIND is not responding off of it's main interface, it IS responding on the
> loopback interface, or on another VIP address on the server not used by
> many clients.
We saw the same type of behavior on our caching servers when I worked at
Genuity 5 years ago. The servers would have trouble responding on the
anycast VIPs that customers used, but were fine when we queried their
individual addresses.
>
> Does BIND maintain separate query queues per interface? Is it possible
BIND doesn't, but I think the OS does.
--
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
More information about the bind-users
mailing list