Windows support has been discontinued in BIND 9.17+ (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14)
Richard T.A. Neal
richard at richardneal.com
Fri Jun 18 16:21:35 UTC 2021
When you say “in Application logs show fine” – how far does named actually get (if at all)? For example whenever I (re)start the “ISC BIND” service on my Windows server I get *loads* of entries in the Application log, starting with these three:
starting BIND 9.16.18 (Stable Release) <id:1c027c4>
running on Windows 10 0 build 17763 1879 for x64
[it’s actually Windows Server being misdetected as Windows 10, but the build numbers are correct]
built with 'with-tools-version=15.0 with-platform-toolset=v141 with-platform-version=10.0.17763.0 with-vcredist=C:/Program\ Files\ (x86)/Microsoft\ Visual\ Studio/2017/BuildTools/VC/Redist/MSVC/14.16.27012/vcredist_x64.exe with-openssl=C:/OpenSSL with-libxml2=C:/libxml2 with-libuv=C:/libuv without-python with-system-tests x64'
From: bind-users <bind-users-bounces at lists.isc.org> On Behalf Of Peter via bind-users
Sent: 18 June 2021 3:51 pm
To: bind-users at lists.isc.org
Subject: Re: Windows support has been discontinued in BIND 9.17+ (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14)
I go back to BIND 9.17.12 and is starts fine install BIND 9.16.18 changed log on to “local system account” like I have done for years go to start BIND get error 1067 in:
The ISC BIND service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
And in Application logs show fine
Maybe its just windows 10 pro? Or is it possible to have bind coded to no longer run in win 10?
On 18/06/2021 3:08 pm, Richard T.A. Neal wrote:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bind-users