Re: failed: out of memory

You'll want to use max-cache-size to enforce a hard limit on the size of your cache. http://www.zytrax.com/books/dns/ch7/hkpng.html#max-cache-size /Tim --- Tim Krzywonos e:: t...@krzywonos.ca Thanks for reminding me of that. Now that I have some confidence that the problem is the

Re: failed: out of memory

Have you tried an rndc flush? You can also dump the contents of the cache to find the (approximate) size of the cache. If related to cache, you can tweak parameters to cache, most namely max-cache-size. IIRC, the cache doesn't have a size limit by default. /Tim I did an rndc

Re: failed: out of memory

You'll want to use max-cache-size to enforce a hard limit on the size of your cache. http://www.zytrax.com/books/dns/ch7/hkpng.html#max-cache-size /Tim --- Tim Krzywonos e:: t...@krzywonos.ca On 2014-07-21 10:57, sch...@adi.com wrote: Have you tried an rndc flush? You can also dump the

Re: failed: out of memory

Have you tried an rndc flush? You can also dump the contents of the cache to find the (approximate) size of the cache. If related to cache, you can tweak parameters to cache, most namely max-cache-size. IIRC, the cache doesn't have a size limit by default. /Tim I did an rndc dumpdb

failed: out of memory

We are running Bind on a Sun Sparc machine running Solairs 8. Bind is built as a 32 bit executable as that is the default and is the way libcrypto and libxml2 are built. We have been running Bind 9.9.5. I am now trying Bind 9.9.6b1 as that claims to have fixed some memory leaks. For some time now

Re: failed: out of memory

Have you tried an rndc flush? You can also dump the contents of the cache to find the (approximate) size of the cache. If related to cache, you can tweak parameters to cache, most namely max-cache-size. IIRC, the cache doesn't have a size limit by default. /Tim --- Tim Krzywonos e::