Plesk DNS management

Manage DNS records for a hosted domain in Plesk

Use Plesk DNS Settings when the domain’s authoritative nameservers are the UKC hosting server’s nameservers. Check that first, back up the current zone, then make the smallest required change.

Confirm authorityPlesk changes matter publicly only when the domain uses that server’s DNS service.

Record the current zonePreserve website, mail and verification records before editing.

Apply and verifySave the change, then query public DNS for the exact hostname.

Before editing

Check where DNS is actually managed

Review the domain’s nameservers in the UKC Domain Control Centre or with a public lookup. Plesk DNS is normally relevant when the domain uses the nameservers assigned to its UKC hosting server, such as a ukc01.uk through ukc13.uk pair.

If the domain uses UKC Parking nameservers, use the Client Area DNS Manager. If it uses an external provider, edit the zone there.

A local Plesk record can exist without being public.

Saving the same record in several panels does not improve propagation and makes future troubleshooting harder.

Record types

Choose the record that matches the service

A / AAAAPoint a hostname to an IPv4 or IPv6 address.

CNAMEMake one hostname an alias of another hostname; do not normally use it at the zone root.

MXDirect incoming email to mail servers using priorities.

TXTPublish SPF, DKIM, DMARC and verification values.

SRVDescribe a service hostname, port, priority and weight.

Protect the current service

Save the existing records

Take screenshots or export/copy the zone before changing it. Record MX and TXT entries even when you are only moving a website. Website and email can use different providers, and replacing the whole zone with defaults can disconnect mail.

Plesk steps

Add, edit or remove a record

1

Log in to PleskOpen the correct UKC hosting service and choose “Log in to Plesk.”

2

Open Websites & DomainsSelect the exact domain and open DNS Settings.

3

Choose the actionAdd a record, click an existing hostname to edit it, or select only the obsolete record before removing it.

4

Enter the required valuesUse the host, target/value, priority and TTL supplied by the service provider.

5

Save and applyComplete any separate Update or Apply confirmation shown by Plesk.

Common mistakes

Avoid outages and invalid DNS

  • Do not delete MX or mail-related TXT records when changing only the website.
  • Do not publish multiple root SPF records; merge authorised senders into one policy.
  • Do not create a CNAME at a hostname that also has other record types.
  • Do not include https://, a slash or a page path in an A, AAAA, CNAME or MX target.
  • Check whether Plesk appends the domain before entering a full hostname.
  • Remove an old record only after confirming the replacement is correct.

Verification

Check the authoritative answer and the service

Query the exact hostname and record type publicly. Confirm the returned value, then test the real service: open the website over HTTPS, send and receive mail, or repeat the provider verification. Caches may continue returning the old answer until its TTL expires.

Need help?

Send the before and intended after state

Include the domain, current nameservers, exact hostname and record type, existing value, required value, provider instructions, time changed and the public lookup result. Explain which website or email service must remain working.

Unsure which zone is active?Open a support ticket before changing nameservers or deleting records. Never send provider passwords or private keys.

Open a support ticket

Was this answer helpful?

« Back