• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved DNSSEC not available on Plesk for Windows

iForced

New Pleskian
Since the suggestion is made in !2016! for support on DNSSEC on Windows, still not a single reaction besides "We will consider" and "Vote". Its a serious thing for security and it should be a priority for Plesk. Now making a topic on the Obidian forum also, so it doesnt get forgotten :)

Please vote! Or Plesk implement this
 
Hi iForced, what nameservers do you use with this Plesk server?
It's easier to sign your domainnames on the nameservers and don't touch your Plesk server.
 
@Paul Hermans I really thought I answered this, but sadly I didn't and then forgot :)

I use Windows DNS as Primary and replicate it to a secondary DNS solution. I tried, but that was the previous version, to sign the zone out of Plesk, but every time a change is made in Plesk, as I want the user to have the ability to change the DNS in Plesk, Plesk would remove the signage entry's. I could make a script to force it everytime after a change, but yeah.. I think this needs to also be in the core features of the Windows version of Plesk.
 
Back
Top