urs I have
dnssec-policy "ecdsa256";
With 9.16.32 and exactly same configuration Bind starts normally without any
errors. This is Master NS.
Other two slave name servers (Windows 2019) starts up 9.16.33 normally without
any errors.
Anyone else having the same problem and any clue how
So I also verify that this problem with vCPU (8) is fixed in the 9.16.21
release.
THANK YOU! ( ❛ ͜ʖ ❛ )✌
T. Sami Leino / Q-Net Oy
Lähettäjä: bind-users Puolesta Richard T.A.
Neal
Lähetetty: torstai 9. syyskuuta 2021 2.16
Vastaanottaja: bind-us...@isc.org
Aihe: RE: BIND 9.16.19 or any
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
erver can be upgraded also. Thank you for pointing the problem for me!
BR, Sami Leino / Q-Net Oy
Lähettäjä: bind-users Puolesta Richard T.A.
Neal
Lähetetty: torstai 19. elokuuta 2021 9.39
Vastaanottaja: bind-us...@isc.org
Aihe: RE: BIND 9.16.19 or any version newer than 9.16.15 does not sta
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ä:
starting.
The ISC BIND service was started successfully.
Br,
Sami Leino
Järjestelmäasiantuntija
+358 40 823 8680
sami.le...@qnet.fi<mailto:sami.le...@qnet.fi>
Q-Net Oy
Yrittäjänkatu 17
65380 VAASA
www.qnet.fi<http://www.qnet.fi/>
[cid:image001.png@01D76C10.C0A40450]
[cid:im
6 matches
Mail list logo
