How to Add and Edit DNS Records in Plesk

In Plesk, DNS records are edited under Websites & Domains > your domain > DNS Settings. A change there affects visitors only if Plesk is serving the domain’s live DNS, so this guide starts by confirming that, then shows you how to change the smallest set of records needed and check the result. It is for Noiz Plesk hosting customers making routine website, mail and verification record changes.

Last reviewed: 13 October 2026, against the current Plesk Obsidian release. This guide is written for Noiz hosting and is kept current against Plesk. It complements, and does not replace, the official Plesk documentation linked below.

Official Documentation Reference

• Configuring DNS for a Domain (Plesk customer guide): primary, secondary and external DNS roles.
• Plesk as the Primary DNS Server (Plesk customer guide): adding, editing and removing records.
• Using External Mail Servers (Plesk customer guide)
• dig reference (ISC BIND documentation)

Prerequisites

• Permission to manage the domain’s DNS in Plesk.
• The exact records supplied by the service you are connecting (website builder, mail provider, verification service).
• A saved copy of the current names, types, values and TTLs of any record you will change, so that you can put it back.

Confirm Where to Make the Change

If your domain uses the Noiz nameservers ns1.noiz.co.za and ns2.noiz.co.za, the records you edit in Plesk DNS Settings are the live ones. If it uses other nameservers, make the change with that DNS host instead. Having a zone in Plesk does not by itself mean the internet uses it. How to Point Your Domain to Noiz Hosting explains nameservers and how to change them.

To check which nameservers a domain uses, replace yourdomain.com with your domain:

dig NS yourdomain.com +short

On Windows, use nslookup -type=NS yourdomain.com instead. How to Find the IP Address of a Website or Domain covers the lookup tools on Windows, macOS and Linux.

This uses your own resolver and may return cached information. If the answer disagrees with what your registrar shows, resolve that before editing. Do not change nameservers, switch off DNS or reset the zone as part of an ordinary record edit.

Add or Edit a Record

1. Go to Websites & Domains and open the domain’s DNS Settings.
2. To add a record, click Add Record and choose the record type. To change an existing record, click its name.
3. Fill in the fields with the values you were given.
4. Click OK.
5. Check that the record list shows the new value. If Plesk shows a prompt to apply pending changes, follow it.

Check the complete resulting name. Plesk shows your domain after the name field, so type only the part before it, such as www. For a record on the bare domain itself, check that the full name shown is yourdomain.com with nothing in front. Do not put a URL, slash or port number in an address or hostname field.

Type	Purpose and common trap
A / AAAA	Point a name to an IPv4 / IPv6 address respectively. Publish only addresses where the intended service works. Check both when moving a website.
CNAME	Point a name to another hostname. It cannot share that name with A, MX or TXT records, so do not create a standard CNAME on the bare domain.
MX	Direct incoming mail to a mail-server hostname. Lower preference numbers are tried first. Use the mail provider’s complete set and priorities.
TXT	Carry verification strings and mail policies. Copy the supplied value exactly and keep unrelated TXT records.

For a service on the bare domain that only supplies a hostname, ask that service for its supported bare-domain setup. Do not guess an A record by resolving the hostname once. The DNS alias rules explain the CNAME restriction.

For SPF, update the existing policy to cover the new sender rather than adding a second v=spf1 record: SPF permits only one policy record per name. For Plesk-signed DKIM with DNS hosted elsewhere, copy the records shown by How to configure external DNS in the domain’s mail settings (Plesk DKIM guide). How to Protect Your Domain from Spoofing and Improve Email Deliverability covers SPF, DKIM and DMARC in more depth.

Allow for Cached Answers

TTL (time to live) controls how long other servers may cache a record. Read the actual TTL shown for the record rather than assuming a default. For a planned change, lower the TTL at least one old TTL period in advance; lowering it during the change cannot expire copies already cached. Restoring a record also takes time to reach everyone, so keep the old website or mail arrangement running during the transition. How to Point Your Domain to Noiz Hosting explains propagation in more detail.

Treat a Mail Move as a Separate Change

Changing MX does not migrate mailboxes or necessarily stop local delivery on the Plesk server. Prepare the destination accounts, existing messages and sending authentication before the cutover, and follow the Plesk external mail guide linked above for the domain’s mail-service setting. Test receiving from an outside sender and from a website on the same hosting, then test sending, and keep the previous arrangement available until those checks pass.

Verify and Recover

1. Query each authoritative nameserver directly. For a domain on the Noiz nameservers, replace yourdomain.com and the record type with the ones you changed:

   dig @ns1.noiz.co.za yourdomain.com A +norecurse
   dig @ns2.noiz.co.za yourdomain.com A +norecurse

2. Look for status: NOERROR, aa in the flags: line and the intended answer. aa means the answer came directly from the nameserver in charge of the domain, not from a cache. Both servers should return the same data.
3. Check a normal resolver afterwards and test the actual website or mail service.

If the authoritative servers disagree, the problem is not just a visitor’s cache: contact us so that we can check the nameservers. If the change itself is wrong, restore only the affected records from your saved values and verify again.

Avoid Reset to Default, which replaces the zone with the server template and removes custom records. Apply DNS Template can also add, change or remove template-derived records and is not an undo button; see Safely Change Plesk DNS Templates and Audit Their Effects.

Need a Hand?

If the DNS controls are missing, the nameservers do not match, or you are on a managed Noiz plan and would prefer us to make the change, contact our support team with the domain and the records you need.