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

Thu Aug 19 06:39:04 UTC 2021

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.

From: Sami Leino <sami.leino at qnet.fi>
Sent: 19 August 2021 6:48 am
To: Richard T.A. Neal <richard at richardneal.com>; bind-users at isc.org
Subject: VS: BIND 9.16.19 or any version newer than 9.16.15 does not start on Windows Server 2019

Hi Richard, and thanks for your reply.

This Windows server 2019 runs on VMware and has 8 vCPU 's. Although any version newer than 9.16.15 just doesn't want to start. I just tried the newest release 9.16.20 also, with exactly same problem.

BR, Sami Leino / Q-Net Oy

Lähettäjä: bind-users <bind-users-bounces at lists.isc.org<mailto:bind-users-bounces at lists.isc.org>> Puolesta Richard T.A. Neal
Lähetetty: keskiviikko 18. elokuuta 2021 18.38
Vastaanottaja: bind-users at isc.org<mailto:bind-users at isc.org>
Aihe: RE: BIND 9.16.19 or any version newer than 9.16.15 does not start on Windows Server 2019

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 a starting point.

Best,

Richard.

From: bind-users <bind-users-bounces at lists.isc.org<mailto:bind-users-bounces at lists.isc.org>> On Behalf Of Sami Leino
Sent: 18 August 2021 10:56 am
To: bind-users at isc.org<mailto:bind-users at isc.org>
Subject: BIND 9.16.19 or any version newer than 9.16.15 does not start on Windows Server 2019

Hello,

Our NS3.qnet.fi which is Windows Server 2019, does not start ISC Bind process with any newer version than 9.16.15

I have tried to update to 9.16.17 , 9.16.18 and the latest 9.16.19, all those versions refuse to start. Nothing reasonable in event viewer. Always same error when trying to start BIND: Windows could not start the ISC BIND service on Local Computer. Error 1067: The process terminated unexpectedly.

Rollback to version 9.16.15 and process starts normally. Named-checkconf does not return anything.

Any ideas, what could be the problem?

C:\DNS\bin>dig -v
DiG 9.16.19

C:\DNS\bin>net start "isc bind
The ISC BIND service is starting.
The ISC BIND service could not be started.

More help is available by typing NET HELPMSG 3523.

Only this version works:

C:\DNS\bin>dig -v
DiG 9.16.15

C:\DNS\bin>net start "isc bind
The ISC BIND service is starting.
The ISC BIND service was started successfully.

Br,

Sami Leino
Järjestelmäasiantuntija
+358 40 823 8680
sami.leino at qnet.fi<mailto:sami.leino at qnet.fi>

Q-Net Oy
Yrittäjänkatu 17
65380 VAASA
www.qnet.fi<http://www.qnet.fi/>

[cid:image001.png at 01D794CD.493D4E40]

[cid:image002.png at 01D794CD.493D4E40]<http://www.facebook.com/QNetOy1994>-[cid:image003.png at 01D794CD.493D4E40]<https://www.linkedin.com/company/q-net-oy>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20210819/0c609d09/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5504 bytes
Desc: image001.png
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20210819/0c609d09/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 773 bytes
Desc: image002.png
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20210819/0c609d09/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 805 bytes
Desc: image003.png
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20210819/0c609d09/attachment-0005.png>