Feature Suggestions
Please provide here your suggestion for new functionality for Plesk. We encourage you to review and vote for suggestions of others. The top-ranked suggestions are likely to be included in the next versions of Plesk.
Please write in English so that voters from all over the world can read and support your request.
Off-topic posts will be removed from here
64 results found
-
Add "issuemail"-property tag for CAA-Records
When creating a CAA record, you can only choose between "issue", "issuewild" and "iodef". Certificate Providers like Sectigo have begun enforcing CAA-Lookups. (See https://www.sectigo.com/knowledge-base/detail/CAA-Record-Certification-Authority-Authorization-1527076091491/kA01N000000zFMO )
For a S/MIME certificate the propery tag needs to be "issuemail". Could you add this to the selection of CAA record property tags?1 voteThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
Add SMIMEA Record in DNS
Add the SMIMEA record in the DNS-system.
This is required for encrypted email communication.There is no need to set up an automatic system, just the option to create an individual record.
The 63-character restriction must be removed, otherwise the hash of the address is too long and will be rejected.
2 votesThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
Cloudflare records exclusions
A very cool feature would be to exclude individual records in the zone from sync / export to Cloudflare and the choice by auto-update to only update / create records without removing whole Cloudflare zone.
In my particular scenario I am serving mts-sts. via Cloudflare worker. Everytime Plesk update DNS zone on Cloudflare the particular mta-sts. record is deleted. This record can not be created in Plesk, because it is a worker trigger.
2 votesThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
Allow to postpone changes to DNS zone
Sometimes it is not convenient to reload all zones on every change, so it would be helpful to have an option to apply changes either immediately, or at a designated time.
2 votesThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
Add method to REST API to manage domain default DNS zone settings (for DNS TTL management)
Currently when using the REST API to get the DNS records of a domain, no TTL values are returned for records unless their TTL values have been changed by the user manually. That's because (by default) DNS records inherit their TTL values from the default DNS zone settings of a domain. However these default DNS zone settings cannot be viewed or managed by the Rest API. Meaning that the default TTL values for DNS records can be viewed using the REST API.
Resulting in a deficiency for users who want to use the REST API to properly manage DNS records.
1 vote -
restrict to edit SOA records for subscription, but allow to manage DNS records
It requires either limit user's ability to change the DNS zone timers (TTL, refresh, expiry...) or to limit them to a preset minimum, while still being able to edit the domain's records.
2 votesThank you for your suggestion. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
-- KvD -
A differential report to compare the DNS template to all or multiple domains on a server
A differential report to compare the DNS template to all or multiple domains on a server to see only items that are "differences" or exceptions to the template, not every DNS entry for a domain.
2 votesThank you for your suggestion. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
-- KvD
-
Hidden Primary DNS without NS RR
in Plesk it is impossible to configure the SOA Primary Nameserver without a NS RR.
The SOA template should support Hidden Primary NameServer and the Zone file generation should always use the Hidden Primary NameServer in the Domain SOA entry.
Example:
@ IN SOA ns1.hidden-primary.tld ...
...
domain.tld. IN NS ns1.secondary.tld.
domain.tld. IN NS ns2.secondary.tld.2 votesThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
Customize MSDNS additional settings directly from Plesk.
Since on Windows Server Bind is going to be dropped, it would be good to customize DNS Settings from MSDNS directly from Plesk.
RDP > DNS app > DNS Server < (right-click) Properties
3 votesThank you for your suggestion. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
-- KvD
-
Bulk add domains and aliases
I would like to add ALIAS DOMAIN in mass.
We often have som domain names similars like .com .net and some other and it take too long time to add on by one.
Please add a field to past all domain to add in alias in one time3 votesThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
DNS Integration for Cloudflare - TLSA records sync
Please consider the possibility of adding synchronization of TLSA records from Plesk to Cloudflare.
https://community.cloudflare.com/t/api-create-a-tlsa-record/262983 votesThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
abilty to add LOC DNS records in Plesk
Add abilty to create LOC DNS records in Plesk. rfc1876
2 votesThank you for your interesting idea! While this is a request for a rarely used DNS record, it still makes sense to enable this record type at least for users who want to link their website to a specific geolocation. We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
Reset DNS record to default value from DNS template
The ability to reset a specific record to the default value from the DNS template. We are currently only able to reset the whole domain.
I'm also missing a column in the dns records overview, displaying which records are default and which are customized. We have to guess at this point which ones are altered.
2 votesThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
DNS record editor for all domains (bulk editing, selective editing)
Editor for all DNS records in the Plesk system, it is very time consuming to mass check records and alter them eg. SPF, DMARC, autodiscover records.
Maybe the editor could also have an option to reset records to DNS template.
4 votesThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
Add support for djbdns / tinydns
Add support for djbdns / tinydns - export each domain's DNS records into a plain text file that gets then copied to separate (stand-alone) DNS server(s) running djbdns / tinydns. The DNS services do not and should not run on Plesk servers themselves, but rather on separate stand-alone servers. Export each domain's DNS zone into domain.com.txt filename.
The text file synchronization can be done either automatically by Plesk, or a simple cron job to automate replication to 2+ djbdns servers, where the files are added, or if a domain.com.txt exists, overwrite it and comile/publish djbdns data.
(we've been using djbdns…
1 voteThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
In the "Domain DNS settings" section, you need to add the ability to temporarily disable records.
Good afternoon. In the "Domain DNS settings" section, you need to add the ability to temporarily disable records.
There is a general list of all records, there is also a checkbox with which you can select the desired lines. By selecting rows through the checkbox, we can only delete in bulk.
Please add the ability to temporarily disable the necessary records during the mass selection of rows through the checkbox. Well, maybe they would just be highlighted somehow or vice versa would be gray, which would mean that they are disabled. Also, if you select these disabled, you could re-enable…2 votesWe will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
Adding DNS records via XML API with custom TTL
It'd be great to have a possibility to add dns records via XML api with an option to specify TTL
2 votesThis is a valid request, so we'll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features.
Thanks in advance!
--
IG
-
Allow DKIM/DMARC/SPF records for the server's hostname domain
This thing that Plesk does not present DKIM public key, referred to server's hostname, is quite annoying. cPanel does, for example.
And I'm not going to mess things up with changing hostname, so to match it with a newly created domain (whose purpose would be just having a DKIM in place).32 votesThank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
-
Do not automatically delete non-Plesk Route 53 records
When making any update to a DNS zone, all records that were not created/synched with Plesk are automatically deleted. This prevents users from using advanced Route 53 functionality, such as aliases (for CDN, load balancer, etc). Because Plesk does not support AWS aliases (which is fair enough), this specific functionality MUST be configured directly in Route 53. That would only be a minor inconvenience, if Plesk didn't actively delete any record not synched with Plesk on any unrelated DNS update. This means Plesk-managed domains can't really use any advanced AWS functionality or Plesk will take the site offline.
If Plesk…3 votesThank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
-
DNS Forwarding
It'd be great to have an option to configure DNS Forwarding with masking in Plesk.
1 voteThank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
- Don't see your idea?