VS: BIND 9.16.19 or any version newer than 9.16.15 does not start on Windows Server 2019

Hi Richard, I will return to this problem with 8 vCPU count. You wrote earlier that there could be a way to have BIND run a specific number of vCPU cores? Because with the current setup we cannot change the server's vCPU count. BR, Sami Leino / Q-Net Oy Lähettäjä: bind-users Puolesta Sami Le

Re: BIND 9.16.19 or any version newer than 9.16.15 does not start on Windows Server 2019

Hi there, On Wed, 8 Sep 2021, Sami Leino wrote: I will return to this problem with 8 vCPU count. You wrote earlier that there could be a way to have BIND run a specific number of vCPU cores? Have you tried searching something like "windows processor affinity"? -- 73, Ged. __

RE: BIND 9.16.19 or any version newer than 9.16.15 does not start on Windows Server 2019

Hi Sami, I'm sorry but I've tried to do that again this evening but I can't get it to work. named.exe can take command line arguments to limit the number of vCPUs it will use, but I can't get this to work when running named.exe as a service. It *should* be the case that you can edit the follow

Re: BIND 'max-cache-size' Value on FreeBSD-13.0

2.5 days in, and 9.11 is still running good, with no crashing. Safe to say that this memory leak is definitely an issue with 9.16. Mark. On 9/6/21 19:30, Mark Tinka wrote: So I've decided to downgrade our busiest resolvers to bind911-9.11.35. Mark. __