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
52 results found
-
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).7 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…2 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
-
Please add the ability to Plesk installer check if bind9 configuration was customized
Please add the ability to Plesk installer check if bind9 configuration was customized
At the moment we have a feature that Plesk pre-upgrade checker shows warnings if custom templates are configured in /usr/local/psa/admin/conf/templates/custom/
Add the same ability but to check if bind9 configuration files are customized at least /etc/default/bind9 file
For example, if the mentioned file was customized after upgrade configuration of the bind9 can be corrupted and service could not be started which lead to the downtime of the websites
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
-
Automatic renewal of wildcard certificates when using Route 53
When renewing a (Let's Encrypt) wildcard-certificate, we first need to go the page for SSL of the specific domain, copy the new code, go to the DNS-page, update the records, go back to the certificate page and click renew. This seems like a lot of manual steps for something that can easily be automated.
I understand this has already been implemented for people who do not use the Route 53 plugin (or other DNS plugins), but since any change in Plesk DNS will automatically propagate to Route 53 with those plugins, I guess this can be fairly easily implemented, saving…
2 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
-
if DNSSEC was signed before DNS is disabled, it should be re-signed with the same keys when DNS is re-enabled.
it should be standard practice to check whether or not the DNSSEC is signed before disabling DNS so that DNSSEC can be re-signed after re-enabling DNS.
A better option would be for Plesk Panel to automatically recognize if DNSSEC was signed before DNS is disabled and then re-signing with the same keys when DNS is re-enabled. If this isn't a possibility, the next best thing would be, if DNSSEC is signed, to provide a warning to the user in the form of a confirmation prompt saying something to the effect that "doing this will unsign DNSSEC and you will need…4 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
-
Ability to edit /etc/resolv.conf via Plesk GUI
It is required to have ability to edit /etc/resolv.conf via Plesk GUI. For example, to adjust or reconfigure DNS servers.
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 -
Handling DNSSEC through CLI
Make it possible to sign DNSSEC through CLI commands instead of only through the DNSSEC Extension in the Plesk GUI.
22 votesThank you for your input! 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.
—
IG -
cli command to delete/modify record from dns template
There is no way to delete/modify record in dns template with cli: plesk bin server_dns. For image automation scripts, it requires to have delete and modify command to manage dns records in template.
2 votesThank you for your input! 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.
—
IG -
Add "Are you sure?" question for disabling DNS zone management.
It happend allready twice to me that i accedently disabled a dns zone because i misclicked the button. Every time it takes about 3+ hours until all dns servers are sync again if this error happens so it would be nice if plesk asks you: "Are you sure?" with a simple yes and cancle button.
12 votesThank you for your input! 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.
—
IG -
support DNAME records (Non-Terminal DNS Name Redirection) - see description
For information: A DNAME-record is used to map / rename an entire sub-tree of the DNS name space to another domain. It differs from the CNAME-record which maps only a single node of the name space.
I would personally appreciate if the full range of records that are available are supported, but with people (especially clients) having multiple things bundled onto single domains into subdomains and correspondent subdirectories, it makes sense more than ever to accommodate these records as many other providers do.
3 votesThank you for your input! 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.
—
IG -
Support Null MX Records
Allow the creation of RFC 7505 Null MX Records.
" A "Null MX" No Service Resource Record for Domains That Accept No Mail"
3 votesThank you for your feature request. We will consider the possibility of its implementation if it becomes sufficiently popular and in demand.
—
IG -
Share One ***** DNS Server for Multiple Plesk Servers
Current we are not able to do this as all Plesk Severs look for "rndc-key" key value in the ***** DNS Server.
It would be great if we can change this "rndc-key" key value so we can configure the key on the ***** Server as rndc-key-1, rndc-key-2, ...
1 voteThank you for your input! 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.
—
IG -
Add ability to set up 128 value for flags field of CAA record
Add ability to set up 128 value for flags field of CAA record as it can be used as security measure.
10 votesThank you for your input! 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.
— AY
-
enlarge dns txt field
At the DNS record edit screen the input field for a TXT record is very small.
Only the first 20 characters are visible.
Please make this field (a lot) larger, there is enough room for.5 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 -
Introduce DNS records multi-column sort.
When required to add a few NS records, it's easy to make typos as DNS records can be sorted by a record type but not sorted by value.
The following sorting is proposed:
1. User Sorts by Value, then the order is: Value (ASC or DESC), Type (ASC), Host (ASC)
2. User Sorts by Type, then the order is: Type (ASC or DESC), Host (ASC), Value (ASC)
3. User Sorts by Host, then the order is: Host (ASC or DESC), Type (ASC), Value (ASC)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 -
Add option to restrict customer access to add/edit DNS records per type
Currently, there is no feature to restrict customer access to edit DNS zones by its type. There is only general DNS zones management permission in Plesk.
There are cases when access to edit particular type of zone should be restricted. For example, if the customer edits the ptr record, it could broke the mail delivery on the server. To prevent such cases from happening, the option would be helpful.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 -
When subscription on source server is deleted after migration do not remove DNS zone on slave DNS
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.
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?