XiaTools

Plesk DNS Settings: How to Add and Modify DNS Records

By Rohit, founder of XiaTools · Updated 18 Oct 2026

Managing your domain name system settings properly ensures that your website, email, and web applications remain accessible to visitors worldwide. When using Plesk, the built-in DNS template and zone editor allow you to take complete control of your domain's routing without needing an external third-party provider. Whether you are pointing a domain to a new server, setting up custom mail exchangers, or adding verification tokens, understanding how to configure your zone files correctly is essential for maintaining high uptime and reliable service.

Accessing the DNS Settings in Plesk

Before you can add or modify any resource records, you need to locate the DNS management interface within your hosting control panel. Depending on your hosting provider, the exact menu layout might differ slightly, but the core path remains consistent across Linux and Windows server environments.

Step-by-Step Navigation

  1. Log in to your Plesk control panel using your administrator or subscription owner credentials.
  2. In the left-hand navigation sidebar or on the main dashboard, click on Websites & Domains.
  3. Locate the specific domain name for which you want to manage your zone file.
  4. Scroll through the tools associated with that domain until you find the DNS Settings icon and click it.

Once inside the DNS Settings page, you will see a list of all active resource records currently associated with your domain, such as A, CNAME, MX, and TXT records. If your domain is configured to use external name servers instead of the local Plesk server, Plesk will display a notification informing you that local DNS changes will have no effect until you switch the domain back to the local master server.

How to Add a New DNS Record in Plesk

Adding a new record is a straightforward process, but you must ensure your syntax matches standard DNS specifications. Let us walk through the process of adding a new record using example.com and documentation IP addresses like 192.0.2.1.

  1. From the DNS Settings page of your domain, click the Add Record button located near the top of the interface.
  2. Select the Record type from the drop-down menu. Common choices include A, CNAME, TXT, MX, and SRV.
  3. In the Domain name field, enter the prefix or subdomain. For example, if you are creating a record for blog.example.com, simply type blog. If you are creating a record for the root domain itself, leave this field blank or enter the @ symbol.
  4. Enter the destination or value in the corresponding field, such as 192.0.2.1 for an A record.
  5. Click OK or Add to save the record to your staging area.
  6. Crucial Step: Notice the yellow notification banner at the top of the screen reminding you to click Update. Until you click Update, your changes are not committed to the active DNS zone file.

Exact Record Syntax Examples

Record Type Domain / Hostname Value / Target Description
A ftp 192.0.2.10 Points ftp.example.com to an IPv4 address
CNAME shop example.com. Creates an alias pointing shop to the root domain
TXT @ v=spf1 ip4:192.0.2.0/24 ~all Configures SPF email security for the root domain
MX @ mail.example.com. (Priority: 10) Directs incoming mail traffic to your mail server

Always remember that trailing dots are important in canonical target fields for fully qualified domain names (FQDN) in BIND zone files. Plesk usually handles trailing dots automatically, but keeping standard practices in mind prevents unexpected resolution failures.

How to Modify or Delete Existing Records

Over time, server migrations, certificate renewals, or service changes require you to update existing configurations. Modifying records incorrectly can instantly break your website or disrupt incoming mail flow.

Modifying a Record

  1. Navigate to Websites & Domains > DNS Settings for your target domain.
  2. Click directly on the name of the record you wish to change (for instance, click on the IP address next to your primary A record).
  3. Update the values in the input boxes as required.
  4. Click OK to save your temporary changes.
  5. Click the Update button at the top of the screen to commit the changes to the live server.

Deleting a Record

  1. Locate the record you wish to remove within the DNS Settings list.
  2. Check the box to the left of the record name.
  3. Click the Remove button.
  4. Confirm the deletion, then click the Update button at the top of the page.

Before making any changes to production domains, it is always wise to use the DNS Lookup tool to inspect your current public records and verify how global resolvers currently view your domain configuration.

Configuring DNS Templates for New Domains

If you manage a hosting server with multiple websites, editing the DNS zone of every single domain individually is inefficient. Plesk provides a master DNS template feature that automatically applies default records to every new subscription or domain created on the server.

Updating the Server-Wide DNS Template

  1. In the left navigation menu of Plesk, click on Tools & Settings.
  2. Under the General Settings group, select DNS Template.
  3. Here, you can add, modify, or remove records that will automatically populate for all future domains.
  4. Click Apply Changes to All Domains if you want to push template updates across existing zones (use this with caution, as it can overwrite customized user configurations).

Common Mistakes and How to Fix Them

Even experienced administrators occasionally run into issues when updating zone files. Recognizing these common pitfalls saves troubleshooting time.

  • Forgetting to click Update: The most common mistake in Plesk is editing a record, seeing it in the local list, and closing the browser. Always verify that you click the yellow Update banner at the top of the page.
  • Missing Trailing Dots on CNAME Targets: When pointing a CNAME to an external domain, failing to include a trailing dot (e.g., entering example.com instead of example.com.) causes the DNS server to append your own domain name to the end, resulting in example.com.yourdomain.com.
  • Ignoring TTL Settings: If you are planning to migrate your server, lowering your Time to Live (TTL) values 24 hours in advance ensures that resolvers cache your records for a shorter duration, making the transition seamless.
  • Conflicting SPF Records: Creating multiple TXT records for SPF causes email authentication failures. Combine all your authorized sending mechanisms into a single SPF record string.

Quick Checklist for Plesk DNS Management

  • Back up your existing DNS zone or note current settings before making edits.
  • Verify that your domain is actively using the local Plesk server for DNS.
  • Enter correct hostnames and values, using trailing dots for external FQDN targets.
  • Save the individual record changes and click the Update banner at the top.
  • Test global propagation and record validity using command-line tools or web utilities.

By following these structured guidelines, you can safely manage your DNS records inside Plesk, avoiding common configuration errors and ensuring your digital assets remain stable and reachable.

Frequently asked questions

Why don't my DNS changes take effect immediately after clicking Update in Plesk?

DNS changes require time to propagate across the internet due to caching by intermediate recursive resolvers and Internet Service Providers. Furthermore, the TTL value of the specific record determines how long local clients continue to store the old record in their cache.

How do I make my domain use external DNS instead of Plesk?

You can switch your domain to use external name servers by updating your registrar's NS records to point to your external provider. Inside Plesk under DNS Settings, you can also disable the local DNS server for the subscription if you no longer wish to host zone files locally.

What should I do if I accidentally break my DNS configuration in Plesk?

If your zone file becomes corrupted or misconfigured, you can restore the default records by clicking the 'Reset to Default' button within the domain's DNS Settings page. Note that this action replaces custom records, so you will need to re-add any specialized verification or routing entries.

Can I manage wildcard DNS records in Plesk?

Yes, you can create wildcard records by entering an asterisk (*) in the domain or host field when adding a new record. This directs all incoming requests for non-existent subdomains to your specified target IP address or server.

How do I check if my Plesk DNS records are configured correctly?

You can verify your DNS records by using command-line utilities such as 'dig' or 'nslookup' to query specific nameservers. Additionally, using online lookup tools helps you see how external resolvers spread across the globe are interpreting your live zone file.

Free tools