hello,

I am using the bind9 included in the netbsd-current src.

In my case, the bind resolvs some hundred thousand requests per day. After 
nearly two days, the bind stops the resolving (no crash). The logfile 
shows the following:

Feb 28 05:08:03 gate named[2859]: /usr/src/dist/bind/lib/dns/cache.c:612: unexpected error:
Feb 28 05:08:03 gate named[2859]: cache cleaner: dns_dbiterator_first() failed:out of memory
Feb 28 05:08:03 gate named[2859]: /usr/src/dist/bind/lib/isc/unix/ifiter_getifaddrs.c:63: unexpected error:
Feb 28 05:08:03 gate named[2859]: getting interface addresses: getifaddrs: Cannot allocate memory
Feb 28 05:40:41 gate named[2859]: cache cleaner could not create iterator: out of memory
Feb 28 05:40:41 gate named[2859]: /usr/src/dist/bind/lib/dns/cache.c:612: unexpected error:
Feb 28 05:40:41 gate named[2859]: cache cleaner: dns_dbiterator_first() failed:out of memory
Feb 28 06:08:03 gate named[2859]: /usr/src/dist/bind/lib/isc/unix/ifiter_getifaddrs.c:63: unexpected error:
Feb 28 06:08:03 gate named[2859]: getting interface addresses: getifaddrs: Cannot allocate memory
Feb 28 07:08:03 gate named[2859]: /usr/src/dist/bind/lib/isc/unix/ifiter_getifaddrs.c:63: unexpected error:
Feb 28 07:08:03 gate named[2859]: getting interface addresses: getifaddrs: Cannot allocate memory


The size of the named starts at nearly 6mb and is increasing to 99mb. If 
the size smaller than 99mb, all works fine, at a size of 99mb the error 
occurs.



My named.conf:

...
options {
         directory "/etc/namedb";
         listen-on-v6 { any; };
         forwarders { aa.bb.cc.dd; ee.ff.gg.hh; };
         notify no;
         datasize 96M;
         max-cache-size 64M;
...


exists there any patches against the problem?


thank you for your efforts
Uwe