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
53 results found
-
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
-
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 -
Automatically enable a DNS zone for newly created subdomains on both the Plesk side and in the DigitalOcean DNS extension
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
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 -
Allow users to create subdomains for whitelisted superzones
Currently you can only disable creating of subdomains for all superzones.
An exclude list to allow some superzones would be nice.
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 -
Automatically activate created domains/subdomains for Microsoft Azure DNS
Automatically activate created domains for Microsoft Azure DNS, perhaps also with "Delegation Set" like for Amazon Route 53 extension.
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 -
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.
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
-
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
-
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
-
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 -
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 -
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 -
Be honest about whether DNS records in Plesk are actually applied
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!
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?