Manage Domain DNS Records in Plesk Safely

Plesk DNS Settings manages a domain’s local DNS zone when the feature and your permissions allow it. First establish whether Plesk is the authoritative DNS provider; an edit to a local zone alone does not update a separate registrar or Cloudflare-hosted zone.

Record the current state

Select the right subscription/domain, identify the delegated nameservers and preserve current records before editing. Note the exact name, type, data and TTL. Plan recovery for website, mail and verification records together instead of treating every row as interchangeable.

Add, modify or remove a record

1. Open the verified HTTPS Plesk account and Websites & Domains > DNS Settings for the intended domain. Administrator and customer views can differ from older screenshots.
2. Choose Add Record, select the required type and enter type-appropriate data. Use a hostname for an MX destination, not an IP.
3. To edit, open the precise existing record, change only the approved fields and save. Review the resulting name to avoid a domain suffix being added twice.
4. To remove, select only the intended row and confirm Remove. Review and apply any pending-change confirmation shown by the installed version.
5. Reopen the record list and verify the final zone values, then check actual authoritative DNS answers.

A default reset is not a narrow rollback

Plesk’s Reset to Default recreates zone contents from the server template and can remove custom records. Do not use it as an automatic fix for one failed record or assume it restores your private before-state. Applying a server-wide DNS template is also distinct from changing a single domain record.

Do not switch primary/secondary DNS roles, disable the zone or change registrar delegation unless those are part of the approved design. A local SOA serial change does not prove every public nameserver serves the same content.

Check service behavior after publication

Compare the intended record at each authoritative server and a recursive resolver. Existing cached answers can remain until their own TTLs expire. Test HTTPS or authorized mail delivery as appropriate; DNS resolution alone does not create mailboxes, certificates or application configuration. If the wrong DNS provider was edited, fix that source rather than repeatedly deleting and recreating the local zone.

Reference: Plesk domain DNS management and reset/template scope.

Reviewed October 15, 2026. Documentation review only; no Plesk zone, template, delegation or customer service was changed.