Memory utilisation problem on busy bind resolver

Hi folks, We are running a number of BIND 9.7.3-p3 caching nameservers. In the last couple of months, we've observed the memory utilisation of named increasing at a steady rate of 1-2% per day on our busiest resolver with no indication of subsiding - on occasion, there have been large step

allowing queries from all IPv4 addresses but only a range of IPv6 addresses

Hello community, I have a requirement to configure BIND 9.7.3 to allow queries from any IPv4 address and only a specific IPv6 prefix. The allow-query statement takes an address match list as argument, but I'm not sure how I can specify 'any IPv4 host' without having to use the 'any' keyword

max-cache-size rule of thumb?

Hi all, Is there a rule of thumb when setting max-cache-size? e.g. max physical memory * 0.4 Is there even a need to set max-cache-size on a server with plenty of memory (10GB) running only BIND? Regards Dennis ___ bind-users mailing list

Resolver issue - drop in qps and memory leak

Hi all, We are running a couple of resolvers using BIND 9.6.2-p2 on FreeBSD 7.1 and are peaking at 10,000 queries per second (qps). Recently, the qps on one resolver dropped dramatically to 3000 during the peak period. The secondary picked up the additional queries and we had a few complaints

Optimising rndc reload times on a slave server with 50,000 zones

Hi folks, I'm looking for suggestions to substantially improve reload times on a slave that is serving 50,000 zones (mostly customer zones). 'rndc reload' is being executed on the slave every 15 minutes. Due to the large number of zones to trawl through, the reload process is causing

Re: Optimising rndc reload times on a slave server with 50,000 zones

would be greatly appreciated. DP On Sun, Feb 27, 2011 at 3:22 PM, Doug Barton do...@dougbarton.us wrote: On 02/26/2011 18:56, Dennis Perisa wrote: Hi folks, I'm looking for suggestions to substantially improve reload times on a slave that is serving 50,000 zones (mostly customer zones). 'rndc