Controlling cache size
Barry Margolin
barmar at genuity.net
Fri Apr 26 18:38:23 UTC 2002
In article <aac678$5ap at pub3.rc.vix.com>, John Fox <jjf at mind.net> wrote:
>
>Hi! My question concerns a BIND 8.3.1-REL installation.
>
>We've a nameserver with a fairly limited amount of RAM (64MB). Left
>unattended, its cache grows to a fairly unwieldy size, drastically
>slowing lookups and impacting upon customer services. I have been
>charged with finding a remedy to this situation.
>
>I immediately siezed upon the 'datasize' option, but was told that
>this does not relate to cache-management per se, and then when the
>datasize limit is hit, the effect will be that named can't get
>any more memory, thus not being able to perform further lookups --
>which would again bring us to a situation in which customer services
>are (greatly) delayed. Not good!
Actually, it will most likely abort. If you combine this with a script
that automatically restarts named when it aborts, you have a solution to
your problem.
BIND 8 doesn't have any other cache limiting mechanism. I think BIND 9 has
added this.
--
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
More information about the bind-users
mailing list