9.16.13 Windows 64-bit - Error 109: The pipe has been ended (when stopped/restarted via Windows Services)
Summary
Error 109: The pipe has been ended (when stopped/restarted via Windows Services)
BIND version used
9.16.13 Windows 64-Bit
named -V
BIND 9.16.13 (Stable Release) <id:072e758>
running on Windows 10 0 build 17763 475 for x64
built by Visual Studio 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'
compiled by MSVC 1916
compiled with OpenSSL version: OpenSSL 1.1.1j 16 Feb 2021
linked to OpenSSL version: OpenSSL 1.1.1j 16 Feb 2021
compiled with libuv version: 1.41.0
linked to libuv version: 1.41.0
compiled with libxml2 version: 2.9.10
linked to libxml2 version: 20910
threads support is enabled
default paths:
named configuration: C:\Program Files\ISC BIND 9\etc\named.conf
rndc configuration: C:\Program Files\ISC BIND 9\etc\rndc.conf
DNSSEC root key: C:\Program Files\ISC BIND 9\etc\bind.keys
nsupdate session key: C:\Program Files\ISC BIND 9\etc\session.key
named PID file: C:\Program Files\ISC BIND 9\etc\named.pid
named lock file: C:\Program Files\ISC BIND 9\etc\named.lock
Steps to reproduce
This behavior already is noticeable with a default install
What is the current bug behavior?
Error 109: The pipe has been ended
What is the expected correct behavior?
Nothing