How to Manage DNS Records in Plesk

DNS records control how your domain name resolves to websites, email services, verification systems, and other internet services. In Plesk, you can manage these records directly from the control panel without using a separate DNS provider interface. This is especially useful in hosting environments where domain, mail, and web settings are managed together.

If your website is hosted on a Plesk server, understanding how to edit DNS records helps you point a domain to the correct server, configure email delivery, connect third-party services, and troubleshoot common domain issues. This guide explains how to manage DNS records in Plesk, what each common record type does, and how to avoid mistakes that can affect website or email availability.

Where DNS settings are managed in Plesk

Plesk includes a built-in DNS management interface for each domain. Depending on your hosting setup, DNS may be controlled by Plesk itself or delegated to an external DNS provider. Before making changes, check whether the domain uses Plesk DNS or custom nameservers.

To access DNS settings in Plesk:

Log in to Plesk.
Go to Domains.
Select the domain you want to manage.
Open DNS Settings.

From this screen, you can view existing records, add new records, edit current ones, remove records, and apply changes. In many hosting environments, DNS changes are not published immediately to the internet. They must be updated and then allowed to propagate based on TTL values and ISP caching.

Understanding common DNS record types in Plesk

Before editing records, it helps to know what the most common DNS entries do. Incorrect DNS changes can interrupt website access, email delivery, or domain verification.

A record

An A record maps a domain or subdomain to an IPv4 address. This is one of the most common records in hosting.

Example: example.com points to 192.0.2.10
Use case: Directing your website to the correct server IP

If your website is hosted on a new server, updating the A record is often one of the first steps.

AAAA record

An AAAA record points a domain to an IPv6 address. It works similarly to an A record, but for IPv6-enabled servers.

Use case: Hosting environments that support IPv6

If your hosting provider gives you an IPv6 address, add or update the AAAA record accordingly.

CNAME record

A CNAME record creates an alias from one hostname to another hostname. It does not point directly to an IP address.

Example: www.example.com points to example.com
Use case: Redirecting subdomains to another canonical host

CNAME records are commonly used for www subdomains, third-party services, and service aliases.

MX record

An MX record specifies where email for your domain should be delivered. If you use mail services in Plesk, MX records are essential.

Use case: Routing incoming email to your mail server
Important: MX records should point to a hostname, not a direct IP address

Incorrect MX records can prevent users from receiving email.

TXT record

TXT records store text data and are widely used for email authentication and domain verification.

SPF configuration
DKIM verification
DMARC policy
Google, Microsoft, and other service verification tokens

TXT records are often required when setting up external email services or verifying ownership for SaaS platforms.

SRV record

An SRV record defines the location of specific services, such as SIP, VoIP, or some messaging platforms.

Use case: Service discovery for applications that support SRV lookups

Not every hosting account needs SRV records, but they are useful for advanced service configuration.

NS record

NS records define which name servers are authoritative for the domain. In many cases, these are set at the registrar rather than in the DNS zone itself.

In Plesk, NS records may appear in the zone file, but changing them inside Plesk does not always change delegation at the registrar. If the domain is using external name servers, modifying records in Plesk may not affect live DNS at all.

How to view DNS records in Plesk

To check the current DNS zone for a domain, open DNS Settings for that domain. Plesk displays all active records in a table. Each entry usually includes:

Record type
Host name
Points to / value
TTL

This overview helps you confirm whether the domain is using the correct web and mail configuration. If a website is not loading or email is misrouted, DNS should be one of the first things to check.

How to add a DNS record in Plesk

Adding a record in Plesk is straightforward, but the value must be accurate. Even a small typo can break service resolution.

Log in to Plesk and open the domain.
Go to DNS Settings.
Click Add Record.
Select the record type you need, such as A, CNAME, MX, or TXT.
Enter the host name and value.
Adjust TTL if needed.
Save the record.
Click Update or Apply Changes if prompted.

After saving, allow time for propagation. Depending on the TTL and resolver caching, updates may take from a few minutes to up to 24–48 hours to fully appear everywhere.

Example: adding an A record for a subdomain

If you want shop.example.com to point to a separate server, you might create:

Type: A
Host: shop
Value: 192.0.2.20

This tells DNS resolvers that requests for shop.example.com should resolve to the specified IPv4 address.

Example: adding a TXT record for verification

When verifying a domain with an external service, you may be asked to publish a TXT value such as:

Type: TXT
Host: @
Value: google-site-verification=abc123...

In Plesk, the host field may be shown differently depending on the interface version. The root domain is commonly represented as @ or left blank.

How to edit existing DNS records

If your domain already has records but they need adjustments, you can edit them directly in Plesk. Common reasons include changing server IPs, updating mail routing, or correcting a previously entered value.

Open the domain’s DNS Settings.
Find the record you want to change.
Click the record name or edit icon.
Update the value, host, or TTL as required.
Save the changes.
Apply the zone update if needed.

Be careful when editing MX, TXT, and CNAME records. These are often tied to mail delivery and external services, so a small change can have broader impact than expected.

How to remove DNS records safely

Deleting a record can be necessary during migrations, cleanup, or service changes. However, removing the wrong entry can cause outages.

Before deleting a record, verify:

Whether the record is still in use
Whether another service depends on it
Whether you have a backup of the zone configuration
Whether the change is part of a planned migration

To delete a record in Plesk:

Open DNS Settings for the domain.
Select the record.
Click Remove or the delete icon.
Confirm the action.
Apply the DNS zone changes.

If you remove a record that is still needed, you can usually add it again, but service interruption may occur while resolvers refresh cached data.

Managing DNS for websites and email in Plesk

In hosting environments, DNS is closely connected to both web hosting and email services. A properly configured zone ensures that visitors reach the website and that email is delivered correctly.

Website-related records

For a standard website hosted on Plesk, the primary records usually include:

A record for the root domain
CNAME or A record for www
AAAA record if IPv6 is used

If the website points to a different hosting server, update these records to the correct IP address or canonical hostname.

Email-related records

Email requires several DNS entries to work reliably:

MX record for incoming mail routing
SPF record in TXT format to define allowed senders
DKIM record for message signing
DMARC record to define handling rules for spoofed mail

Plesk often helps generate or manage mail authentication records, but you should still verify that they are published correctly in the active DNS zone.

How TTL affects DNS changes

TTL stands for Time To Live. It tells DNS resolvers how long to cache a record before checking for updates.

A lower TTL can make changes propagate faster, which is useful during migrations or troubleshooting. A higher TTL reduces lookup traffic but can delay updates.

Practical examples:

Short TTL: useful before moving a website to a new server
Default TTL: suitable for stable production records
Long TTL: may be used for rarely changed records

If you are planning major DNS changes, reduce TTL in advance if possible. This can help the new settings take effect more quickly once you update the zone.

Best practices for DNS management in Plesk

Managing DNS in a hosting control panel is easier when you follow a few operational best practices.

Keep a backup or screenshot of the existing zone before major changes.
Change only the records you need to modify.
Use accurate hostnames and values, especially for MX and CNAME records.
Verify whether DNS is hosted in Plesk or elsewhere before editing.
Allow time for propagation after applying updates.
Test website and email functionality after each change.
Check for duplicate records that may conflict with each other.

For managed hosting environments, it is also good practice to document which service owns each DNS record. This makes future troubleshooting easier and reduces the risk of accidentally overwriting entries used by applications, email platforms, or external integrations.

Common DNS issues in Plesk and how to troubleshoot them

When DNS-related problems appear, they often look like website or mail issues. In reality, the cause is usually a missing, incorrect, or unpublished record.

Website is not resolving

If the domain does not open in a browser, check the A record, AAAA record, and nameserver delegation. Make sure the domain points to the correct hosting IP address and that the zone changes were applied.

Also verify whether the domain uses Plesk DNS or external DNS. If an external provider is authoritative, changes made in Plesk may not have any effect.

Email is not being delivered

For mail delivery problems, inspect the MX records first. Confirm they point to the correct hostname and that the hostname itself resolves properly. Then check SPF, DKIM, and DMARC TXT records, especially if outgoing messages are landing in spam or being rejected.

Changes are not visible yet

If recent edits are not showing up, this may be due to propagation delay or caching. Use tools such as nslookup or online DNS checkers to verify whether the zone has updated globally.

Remember that some resolvers cache old data until the TTL expires. If the record was changed recently, the old result may still appear in some places temporarily.

Conflicting records

Sometimes a hostname has multiple records that create confusion. For example, a host may have both a CNAME and an A record, which is not valid in most DNS setups. Review the zone carefully and remove conflicting entries.

Using Plesk with external DNS providers

Not all Plesk installations host DNS for every domain. Some setups use Cloudflare, registrar DNS, or another external provider. In those cases, Plesk may still show DNS settings, but live resolution is controlled elsewhere.

If your domain uses external DNS:

Edit records at the authoritative DNS provider.
Use Plesk only for local reference or server-side configuration if applicable.
Confirm nameserver delegation at the registrar.

This distinction is important in hosting support workflows. A frequent issue is updating a zone in Plesk while the domain continues to resolve from another DNS service.

Recommended records for typical hosting setups

While every domain is different, a common Plesk-based hosting configuration may include the following:

A record: root domain to server IP
CNAME record: www to root domain or a target host
MX record: mail host for the domain
TXT SPF record: authorizing mail senders
TXT DKIM record: public signing key
TXT DMARC record: mail policy and reporting

These records provide a solid baseline for web hosting and email operation in a managed hosting environment.

FAQ

Can I manage DNS completely inside Plesk?

Yes, if Plesk is the authoritative DNS host for the domain. If the domain uses external nameservers, you must manage DNS there instead.

How long do DNS changes take to work?

It depends on the TTL, resolver caching, and the provider. Some changes appear in minutes, while others may take up to 24–48 hours to fully propagate.

What is the difference between an A record and a CNAME record?

An A record points directly to an IPv4 address. A CNAME record points one hostname to another hostname. CNAMEs are commonly used for aliases such as www.

Why is my email not working after a DNS change?

The most common causes are incorrect MX records, missing SPF/DKIM TXT records, or DNS changes being made in the wrong place. Check whether the authoritative DNS is in Plesk or with another provider.

Can I create a CNAME for the root domain?

In standard DNS, the root domain usually cannot use a CNAME record because it also needs other essential records. Use an A record for the root domain in most hosting setups.

Should I change TTL before migrating a website?

Yes, lowering TTL ahead of a migration can help new DNS values propagate faster. After the migration, you can raise it again if desired.

What should I do if I accidentally delete a DNS record?

Restore it as soon as possible using your backup or the previous zone values. Then verify website and email functionality after the record is re-added.

Conclusion

Managing DNS records in Plesk is a core part of domain, website, and email administration in hosting environments. Whether you are updating an A record for a new server, adjusting MX records for mail delivery, or adding TXT records for verification, the DNS zone must be accurate and consistent.

In Plesk, the DNS Settings interface gives you direct control over the records that shape how your domain behaves on the internet. The key is to confirm where DNS is hosted, edit only the necessary records, and verify the results after each change. With a careful approach, you can maintain reliable website access, stable email delivery, and smooth integration with external services.