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

64 results found

  1. comments for DNS

    Add comments filelds for DNS records.

    8 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)
  2. "Keep DNS zone" when a domain is deleted

    Please add functionality to "Keep DNS zone".

    It would allow keeping the DNS zone of a domain when this domain is deleted.

    This is useful, for example, if you move an account to a different server that is a part of the same DNS cluster as the previous server, and you want to delete the account information from the original server.

    The same functionality is implemented in cPanel:
    https://documentation.cpanel.net/display/68Docs/Terminate+Accounts

    7 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)
  3. 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"

    6 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. Disable DNS when Subscription is Disabled

    When a Subscription is Disabled, DNS records are currently still served for the domain. When email and/or websites are hosted remotely, Disabling the Subscription in Plesk therefore has no real effect.

    Keeping the DNS records active when the Subscription is merely Suspended seems correct. But keeping them enabled when the Subscription is Disabled is not ideal with remotely-hosted email or web.

    Obviously simply disabling DNS for the domain resolves the problem, but I think it should be automatic when the domain is Disabled rather than just Suspended.

    6 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. Ability to create custom MX records via DNS Templates with <domain> placeholder in the middle

    Ability to create custom MX records via DNS Templates with <domain> placeholder in the middle of the value.

    For example, currently, it is not possible to create a record via DNS Templates:
    <domain>. MX mx.<domain>.example.com

    It can be useful for setting up an external mail service with a hostname based on a domain name.

    6 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)
  6. 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…

    5 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. 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 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)
    open discussion  ·  IgorG responded

    Thank 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

  8. Please automate DNS for Certification Authority Authorization (CAA)

    After adding a certificate for a domain, plesk could add automatically the right DNS settings for CAA.

    Example: Adding a certificate from Let's Encrypt, Plesk could add an CAA Record with the right tags.

    Until now i added the records for Let's Encrypt in the DNS template, which is okay. The records needs to be changed manually, if a different certificate was installed.

    5 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)
    open discussion  ·  IgorG responded

    Thank 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

  9. 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.

    4 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)
  10. 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.

    4 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)
    open discussion  ·  IgorG responded

    Thank 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

  11. Customize MSDNS additional settings directly from Plesk.

    Since on Windows Server Bind is going to be dropped, it would be good to customize DNS Settings from MSDNS directly from Plesk.

    RDP > DNS app > DNS Server < (right-click) Properties

    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)
  12. Bulk add domains and aliases

    I would like to add ALIAS DOMAIN in mass.
    We often have som domain names similars like .com .net and some other and it take too long time to add on by one.
    Please add a field to past all domain to add in alias in one time

    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

    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)
  13. 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…

    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

    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. 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…

    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)
  15. 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 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)
  16. 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 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)
  17. Add the ability to apply DNS Template to existing domains on Windows

    This feature exists on Linux. So it will be great to have the same on Windows as well. It will make it easier to manage DNS on servers with many domains.

    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)
    open discussion  ·  IgorG responded

    Thank 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

  18. Raw SOA Editor

    I want to change the DNS-Editor to the Raw View like a Source Editor for HTML.

    Its way better to import dns from other providers to plesk with the raw soa file format if there are too much records to single add them via gui.

    Maybe a Button "Extended View" with default SOA Design

    $TTL 7200
    @ IN SOA ns1.your-server.de. postmaster.your-server.de. (
    2019101403 ; serial
    86400 ; refresh
    10800 ; retry
    3600000 ; expire
    86400 ) ; minimum

    @ IN NS ns3.second-ns.de.
    @ IN NS ns.second-ns.com.
    @ IN NS ns1.your-server.de.

    @ IN A 1.1.1.1
    www IN A 1.1.1.1

    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)
  19. 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)
  20. 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)
  • Don't see your idea?

Feedback and Knowledge Base