bind cache size

[Brad Knowles]

At 3:20 PM +0100 5/15/01, Chris Pile wrote:

>  From experience, the cache did not settle after 1-2 weeks.  Over a
>  period of about one month the cache gradually grew larger and larger,
>  until it eventually started eating into swap and affected the response
>  time of lookups.

	With older versions of BIND, I believe that there were one or 
more memory leak problems which might have been a cause of problems 
for some sites.  This may have been fixed in 8.2.4, I'm not sure.

>  Sorry Brad, but can you explain this configuration a little, I found it
>  hard to work out what you meant, sounds good though ;)

	On each machine, run a caching-only copy of named.  Put the 
machine itself as the first IP address in /etc/resolv.conf.  As you 
add more machines, each will be doing their own DNS resolution, and 
you will scale linearly.

-- 
Brad Knowles, <brad.knowles at skynet.be>

/*        efdtt.c  Author:  Charles M. Hannum <root at ihack.net>          */
/*       Represented as 1045 digit prime number by Phil Carmody         */
/*     Prime as DNS cname chain by Roy Arends and Walter Belgers        */
/*                                                                      */
/*     Usage is:  cat title-key scrambled.vob | efdtt >clear.vob        */
/*   where title-key = "153 2 8 105 225" or other similar 5-byte key    */

dig decss.friet.org|perl -ne'if(/^x/){s/[x.]//g;print pack(H124,$_)}'