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.
For technical assistance, contact Plesk support
For questions, bug reports, discussions and free assistance, check our Forum and Facebook page
For additional information, see Documentation, Knowledge Base and Blog
Follow us on Twitter for more news on Plesk development
Off-topic posts will be removed from here
-
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 vote -
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
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 custom dns recursion settings via Plesk GUI or CLI and avoid overwriting by Plesk
Going to Tools & Settings > DNS Template > DNS Recursion Settings, it's not possible to set a custom list of IPs or hostnames, it's only possible to choose between different options: any host, localnets, localhost.
As a workaround to this limitation, i'ts required to customize the options section in the /etc/named.conf file, but it gets overwritten by Plesk.
Please, add the possibility to customize the dns recursion settings via Plesk GUI and to keep the custom allow-recursive set in /etc/named.conf file.
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 -
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.
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 -
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.
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 -
Disallow multiple SPF records
At the moment it is possible for customers to add more than one SPF record making the configuration invalid.
Plesk should disallow multiple SPF records.
Plesk should give an error and an automatic merge suggestion.
EXAMPLE:
"Error you can only have one SPF record."
This is your current SPF record: <current SPF>
You tried to add: <extra SPF>
automatic merge suggestion: <combined suggestion>
[OK Button]1 vote -
changing ***** to Master DNS mode without reverting to default ***** DNS records
changing DNS to Master DNS mode without reverting to default DNS records
1 vote
- Don't see your idea?