I agree! BIND 9.16.21 is working just fine for me on Windows Server 2019 with
either 8 or 12 vCPUs.
Thanks, ISC BIND team.
Richard.
From: Sami Leino
Sent: 17 September 2021 8:49 am
To: Richard T.A. Neal ; bind-us...@isc.org
Subject: VS: BIND 9.16.19 or any version newer than 9.16.15 does not
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
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.
Hi Sami,
Could you try changing the number of vCPUs to either 6, 7, 9, or 10 and see if
it then starts OK? If that works then you can either leave it like that or we
can help you with a way to have BIND run a specific number of vCPU cores while
you put the VM back to 8 vCPUs.
Best,
Richard.
Hi Sami,
There's presently an issue where the ISC BIND service (v9.16.19) won't start on
a Windows server with either 8 or 12 vCPUs. How many CPUs (or vCPUs) are in
this Windows Server?
I didn't find that older versions were exhibiting the same issue so it might
not be that, but it's at least
5 matches
Mail list logo
