Add abilty to create ALIAS or ANAME DNS in Plesk. To point the "naked" version of your domain (like example.com ), because this is not posible with the CNAME ( RFC1912 section 2.4:)

Please add the possibility to add a CNAME for rootdomain instead of an A-record, so-called CNAME flattening feature.

This feature exists on Linux. So it will be great to have the same on Windows as well. It will make it easier to manage DNS on servers with many domains.

After a migration the DNS zone for a subscription should not be removed from slave servers configured with Slave DNS Manager extension, if Plesk server is not the master for the zone.

Support underscore for DNS record creation, e.g.,

add NS records for default._domainkey.example.com

After adding a certificate for a domain, plesk could add automatically the right DNS settings for CAA.

Example: Adding a certificate from Let's Encrypt, Plesk could add an CAA Record with the right tags.

Until now i added the records for Let's Encrypt in the DNS template, which is okay. The records needs to be changed manually, if a different certificate was installed.

Would be nice to get some extension for plesk users so they can switch mx from default to G Suite Gmail in "one click".

Similar to Remote MX Wizard for cPanel
https://www.gk-root.com/GK-Apps/Remote-MX-Wizard/

Add the functionality to modify the notify-to-soa option from within Plesk and make it persistent.

Right now it can be done as per the workaround shown here: https://support.plesk.com/hc/en-us/articles/115001713434

However, this solution is not persistent as the file /etc/named.conf gets overwriten everytime a change is made in Plesk.

The DNS records in Plesk pretend as though they're actually being applied to the domain, but this is FALSE. The nameservers of my domain are not set to my domain's name. You need to compare the actual nameserver records and to the ones in the Plesk settings before acting like you're the name server for my domain.

Case in Point: https://webmasters.stackexchange.com/questions/123260/the-plesks-name-server-acts-as-the-primary-name-server-for-the-dns-zone-what

Plesk is nice, but this is not nice!

Currently, only version 6.0 is supported. It would be great to add for SimpleDNS version 8.0 on as well.

The ability to configure several master servers for ***** server with the corresponding checks (for example, check if a domain already exists on one of master server than block creation of domain on another master server)

Add comments filelds for DNS records.

It would be great if after the new subdomain is created, its DNS zone automatically enables on both Plesk side and in the DigitalOcean DNS extension

Option to add a note to a DNS entry.

Would it be possible to sign a domains DNSSEC through the API and export the public key?

This would be nice to have in combination with a domainregistar outside of Plesk.

This is something that really should be available by now, especially as it's available for DO and AWS.

Possibility to add NAPTR records in Plesk

Please add functionality to "Keep DNS zone".

It would allow keeping the DNS zone of a domain when this domain is deleted.

This is useful, for example, if you move an account to a different server that is a part of the same DNS cluster as the previous server, and you want to delete the account information from the original server.

The same functionality is implemented in cPanel:
https://documentation.cpanel.net/display/68Docs/Terminate+Accounts

I want to change the DNS-Editor to the Raw View like a Source Editor for HTML.

Its way better to import dns from other providers to plesk with the raw soa file format if there are too much records to single add them via gui.

Maybe a Button "Extended View" with default SOA Design

$TTL 7200
@ IN SOA ns1.your-server.de. postmaster.your-server.de. (

2019101403   ; serial

86400        ; refresh

10800        ; retry

3600000      ; expire

86400 )      ; minimum

@ IN NS ns3.second-ns.de.
@ IN NS ns.second-ns.com.
@ IN NS ns1.your-server.de.

@ IN A 1.1.1.1
www IN A 1.1.1.1

When a Subscription is Disabled, DNS records are currently still served for the domain. When email and/or websites are hosted remotely, Disabling the Subscription in Plesk therefore has no real effect.

Keeping the DNS records active when the Subscription is merely Suspended seems correct. But keeping them enabled when the Subscription is Disabled is not ideal with remotely-hosted email or web.

Obviously simply disabling DNS for the domain resolves the problem, but I think it should be automatic when the domain is Disabled rather than just Suspended.