Skip to content

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

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

62 results found

  1. Allow CNAME to point to another CNAME

    Allow CNAME records to point to another CNAME record. Currently it is not possible to do so in Plesk and shows the error:

    Error: Incorrect combination of DNS records is present in the DNS zone.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Could you please give an example why a CNAME needs to point to another CNAME and cannot point directly to the target? -- PD

    -----

    A CNAME can point to another CNAME, although this configuration is  generally not recommended for performance reasons. When applicable, the  CNAME should point as closely as possible to the target name in order to  avoid unnecessary performance overheads.  But 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

  2. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. <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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. DNS Acl removal via CLI

    Meanwhile it's possible to add DNS ACL via CLI:
    plesk bin server_dns -u -add-acl 192.0.2.78,192.0.2.0/24

    There are no native tools in CLI for removing it.

    Adding such feature would be great.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Add <ip1>, <ip2>, <ip3> placeholders to DNS template

    Mail server on windows sends email from specific IP
    It's required to setup SPF record in DNS template to include all server public IP addresses.
    If mail server outgoing IP and public IP is changed in the future, the DNS will update the new IP automatically for all domains.

    Example: "v=spf1 ip4:<ip> ip4:<ip2> ip4:<ip3> ~all"

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Restrict Digital Ocean DNS extension for specific users/roles

    Please add an option to restrict usage of Digital Ocean DNS extension for some of the users

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. I would like to print out the DNS-Settings!

    Please built a Button to print out the Settings of the DNS!

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. DNS Forwarding

    It'd be great to have an option to configure DNS Forwarding with masking in Plesk.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Set MX priority 100 or customize to any value

    Possbility to add MX record with priority 100 but plesk allows only to select priorities from 0 to 50. For example to enable mail server to work properly at the OVH they require the configuration to priority 100

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    The actual value of an MX priority does not influence the behavior of other servers directly. It is more a "sorting" criteria. When OVH asks for "100" in a list of their five MX servers as 1, 5, 50, 100, 200, you can also rearrange that list to values like 1, 5, 10, 15, 20 with 15 representing the 100, because it is in the same order "slot" as their manual suggests. Currently you can configure ten MX entries for the same domain, but in real-world configurations we've never encountered a domain where ten MX entries were needed. 

    If you know of an example where a provider asks for a fixed value like "100" and does not deliver mail if that value is not present in an MX record, please let us know in your comments.

    -- PD

  19. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base