Configure Plesk DNS Zone Management: Complete Records Tutorial

Understanding Plesk DNS Zone Management

DNS zone management in Plesk controls how domain names resolve to server IP addresses. Every domain needs properly configured DNS records to function—your website, email, subdomains, and third-party services all depend on accurate DNS settings.

When you configure Plesk DNS zone management, you create a roadmap telling the internet where to find your services. One misconfigured record can break your website or email within hours.

Plesk offers an intuitive interface for managing these records. You'll primarily work with A records for websites, MX records for email, and CNAME records for aliases.

Accessing DNS Zone Settings in Plesk

Log into your Plesk control panel and select the domain you want to manage. Click "DNS Settings" from the domain management menu to see existing DNS records that Plesk created automatically.

Default records include an A record pointing to your server's IP, MX records for email, and often a CNAME record for the www subdomain. These handle most common scenarios, but you'll likely need custom records for specific requirements.

Write down current record values before making changes. This creates a quick backup if you need to revert anything.

Configuring A Records for Website Hosting

A records map domain names directly to IPv4 addresses. Your main domain typically points to your server's primary IP address through an A record.

To add a new A record, click "Add Record" and select "A" from the dropdown. Enter the subdomain name—like "blog" for blog.yourdomain.com—then add the destination IP address.

Set TTL to 3600 seconds for most cases. This tells other DNS servers how long to cache the record before checking for updates. Lower values allow faster changes but increase query load.

For Hostperl VPS customers, your server IP appears in the client area and welcome email. Contact support if you need confirmation.

Setting Up CNAME Records for Subdomains

CNAME records create aliases pointing to other domain names instead of IP addresses. They're perfect for subdomains that should follow your main domain's IP address.

Select "CNAME" as the record type, enter the subdomain name, and add the target domain in the "Canonical name" field. For example, create a CNAME for "www" pointing to "@" (your root domain).

CNAME records cannot exist at the root level—you can't create one for the bare domain itself. Use A records for root domain configurations.

Third-party services often require CNAME records. CDN providers like CloudFlare provide CNAME targets to configure. SSL certificate verification may also need temporary CNAME records.

Configuring MX Records for Email Delivery

MX records tell other mail servers where to deliver email for your domain. Multiple MX records with different priorities provide backup options and load distribution.

Plesk automatically creates MX records pointing to your server when you enable email hosting. The default setup works for most scenarios, but external email services like Google Workspace require MX record changes.

Select "MX" as the record type and enter the mail server hostname. Set priority values where lower numbers indicate higher priority—most setups use 10, 20, and 30.

Email delivery continues using old records during DNS propagation, which takes 1-4 hours typically but can extend to 24-48 hours depending on TTL settings.

Adding TXT Records for Verification

TXT records store text-based information for domain verification and email authentication. Common uses include SPF records for email security, domain ownership verification, and DKIM keys.

Select the TXT record type and enter the required text string exactly as provided by your service. SPF records typically start with "v=spf1" and list authorized mail servers.

Google and similar services use TXT records for domain ownership verification. These usually have specific names like "google-site-verification" with long random strings. Don't modify these verification strings.

Our VPS hosting solutions include full DNS management capabilities without restrictions on record types.

Managing DNS Record Priority and TTL Values

Priority values matter for MX and SRV records. Lower numbers receive traffic first. When the primary server fails, email automatically falls back to higher-priority servers.

TTL values control DNS caching behavior. Short TTLs (300-900 seconds) allow rapid changes but increase server load. Long TTLs (3600-86400 seconds) improve performance but delay change propagation.

Use short TTLs when planning DNS changes or server migrations. Switch to longer values once your configuration stabilizes to reduce unnecessary queries and improve loading times.

Consider caching impact during outages. Server failures combined with long TTLs can extend downtime until cached records expire.

Troubleshooting Common DNS Configuration Issues

DNS propagation delays cause most configuration problems. Changes take several hours to reach all global DNS servers. Use online DNS checking tools to verify proper propagation.

Conflicting records create unpredictable behavior. You can't have both CNAME and A records for the same subdomain name. Remove conflicts before adding new records.

Syntax errors in TXT records break verification processes. Copy and paste TXT values exactly as provided—extra spaces or modified characters cause failures.

Missing trailing dots in DNS record values can cause resolution problems. Some configurations require fully qualified domain names ending with a period. Check your service documentation for specific formatting requirements.

Testing DNS Zone Configuration

Test your DNS setup using command-line tools like dig or nslookup. These query DNS servers directly and show exactly what records return for your domain.

Run "dig yourdomain.com" to check A records, "dig MX yourdomain.com" for mail records, and "dig TXT yourdomain.com" for text records. Compare results with your Plesk configuration to spot discrepancies.

Online DNS testing tools provide web-based alternatives to command-line utilities. Services like DNSChecker.org show DNS resolution from multiple global locations, helping identify geographic propagation issues.

Monitor website and email functionality after DNS changes. Set up basic monitoring alerts to catch resolution failures quickly and prevent extended downtime.

Frequently Asked Questions

How long does DNS propagation take after configuring Plesk DNS zone management?

DNS propagation typically completes within 1-4 hours for most record types. TTL settings and global DNS caching can extend this to 24-48 hours in some cases. MX record changes may propagate slower than A or CNAME records.

Can I use external DNS servers instead of Plesk DNS management?

Yes, you can point your domain to external DNS servers like CloudFlare or Route53. Change nameservers at your domain registrar to the external provider. You'll lose Plesk's DNS interface but gain advanced features like global load balancing.

What happens if I delete a DNS record by mistake in Plesk?

Deleted records stop resolving immediately for new DNS queries. Cached records continue working until their TTL expires. Restore deleted records quickly using the same configuration values. Contact your hosting provider for help recovering original settings.

How do I configure DNS records for a subdomain hosted on a different server?

Create an A record for the subdomain pointing to the external server's IP address. Alternatively, use a CNAME record pointing to the external server's domain name. The subdomain will resolve independently of your main domain's hosting location.

Why are my DNS changes not taking effect even after several hours?

Check for syntax errors in your record configuration, conflicting records with identical names, or incorrect TTL settings. Verify that your domain's nameservers point to your hosting provider's DNS servers. Local DNS caching on your computer or network may also delay visible changes.