Jan Schaumann via bind-users <bind-users@lists.isc.org> wrote: > Greg Choules <gregchoules+bindus...@googlemail.com> wrote:
> > - Are you stuck on 9.16.30 for some reason? If not, grab the latest 9.18 > > package. It will be less memory hungry generally and contain fixes for > > recent issues. > > Yeah, will give that a try. Upgrading to 9.18.11 by itself did not help, but setting an explicit 'max-cache-size' does seem to. The queries I'm doing right now are all unique second-level domain queries, so no caching takes place, while at the same time the cache grows proportionally with the queries. I'm guessing that without a set 'max-cache-size', this continues to grow until there is no more memory space left, we start swapping, and eventually get OOM killed. https://bind9.readthedocs.io/en/v9_18_11/reference.html claims that the default 'max-cache-size' is 90% of physical memory, but it seems that didn't work out here. Might it be that on NetBSD, bind doesn't correctly determine the physical memory amount? -Jan -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users