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
60 results found
-
Lock DNS records | Disable Reset to default
We have the "dmarc"- record in our template having a placeholder for the value. At the time the Record "dmarc" was edited by adding the value, mostly every DNS record is no more in the state of the DNS template.
Therefore it is important to have some policies:
- The button "Reset to default" can be disabled on Admin and Reseller level.
- The button "Master/*****" can be disabled. Usually this functionality is not needed.
- For certain very important DNS setting, a "Lock" button might make sense. If applied, this record can not be edited anymore by…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.
— AY
-
<hostname> variable in DNS Template
Hello!
Im running a multiserver network where all emails are sent from a service nodes main ip. And I want to have the following MX record in my DNS template: MX | <domain> | <hostname>| .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.— rk
-
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
-
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/262982 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
-
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
-
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 -
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)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 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 -
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 -
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 -
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?