Memory Leak in Bind 9?

[Wes L. Zuber]

After using Bind for years with the same relative configuration we  
started to see named stop responding.

Looking at the logs I see this:

Dec 08 01:28:53.584 general: error: timer.c:603: unexpected error:
Dec 08 01:28:53.585 general: error: couldn't allocate event

this is bind 9.2.2 on FreeBSD 4.4. I do see some other posts for the  
same issue on this list without and answer for FreeBSD 5.5.

As I said this just suddenly started occurring. We have a cronjob to  
restart named twice a day to keep it living.

Anyone have any ideas?

Thanks,

--Wes