Issue Bind DNS for Windows Removed on Plesk 18.0.70

[rafaelgrecco]

Server operating system version

Windows Server 2016

Plesk version and microupdate number

18.0.72

As the title says, I did not know that Plesk for Windows was removing Bind DNS, and I ended up updating my installation.

After some days, I noticed that both my secondary DNS servers were outdated. After some troubleshooting, I found out that the rndc utility was gone, and finally discovered that Plesk had removed Bind DNS support.

I was using Slave DNS Manager to synchronize my primary DNS (running on Plesk for Windows) with my two secondary DNS servers (both running BIND DNS on Linux).

How can I synchronize my DNS servers now? This is a production server with hundreds of domains, so it is an urgent matter.

Thanks.

 

[scsa20]

There's been multiple notices about BIND being removed from Windows since the people who created BIND decided to drop supporting Windows few years ago.

With that said, you can still easily integrate the Windows DNS servers with your BIND servers, you need to do a bit of configuration to make sure to allow zone transfers between the 2. See Integrating Windows DNS into an existing DNS namespace - Windows Server

 

[AYamshanov]

You can continue using Slave DNS Manager on Plesk for Windows, but you need to put the rndc.exe file on the server. This is required since BIND is no longer distributed with Plesk. Adding this file to the server also means you take responsibility for this part of the integration, which is important as the BIND vendor has ended support for Windows.

P.S. We have several different ways to monitor changes in Plesk (including deprecations): the Plesk Changelog and a separate page with the Deprecation Plan.