Configuring Domain Mail Servers via Plesk Obsidian Panel

Configuring your mail server settings properly requires updating your plesk dns mx records so that incoming emails reach your inbox instead of bouncing back to senders. Whether you are hosting your email on the same server or routing it through an external provider like Microsoft 365 or Google Workspace, getting these DNS entries right is critical for reliable communication. In this guide, we will walk through the exact steps, syntax, and troubleshooting techniques needed to manage mail exchanger records inside the Plesk Obsidian control panel.

Before making changes, it is always a smart practice to verify your current email routing configuration using the MX Lookup tool on XiaTools, which quickly inspects your domain's live mail servers and highlights any propagation or priority discrepancies.

Understanding Mail Exchanger Records and Priority

A Mail Exchanger (MX) record is a type of resource record in the Domain Name System that specifies the mail server responsible for accepting email messages on behalf of a domain name. Each MX record consists of two primary components:

• Priority (Preference): An integer value (such as 10, 20, or 50) that indicates the order of preference. Lower numbers mean higher priority. Sending mail servers always attempt to deliver mail to the lowest available priority number first.
• Destination (Target Host): A fully qualified domain name (FQDN) pointing to the actual mail server handling the traffic, such as mail.example.com.

When multiple MX records exist, backup or secondary mail servers with higher priority numbers (e.g., 20) catch incoming mail if the primary server with a lower priority number (e.g., 10) goes offline.

Local vs. External Mail Routing

Depending on your infrastructure, your plesk dns mx records will point to different destinations:

• Local Mail Server: Mail is handled by the Postfix or Dovecot service running on your Plesk server. The destination is usually mail.example.com or directly your domain root.
• External Mail Provider: Mail is routed to third-party services like Google Workspace or Microsoft 365. You must use the exact hostnames and priorities provided by those vendors.

Routing Type	Typical Destination Hostname	Recommended Priority	Use Case
Local Plesk	mail.example.com	10	Standard hosting where Plesk manages email accounts.
Google Workspace	aspmx.l.google.com	1	Using Google for business email.
Microsoft 365	example-com.mail.protection.outlook.com	0 or 10	Using Exchange Online for corporate email.

Step-by-Step Configuration in Plesk Obsidian

Configuring or modifying your mail records in the Plesk Obsidian panel takes only a few minutes. Follow these steps to update your zone file accurately.

Step 1: Access the DNS Settings

1. Log in to your Plesk Obsidian control panel.
2. In the navigation sidebar, click on Websites & Domains.
3. Locate the domain you want to configure and click on DNS Settings. (Note: Menu paths and button names may differ slightly depending on your hosting provider's custom skins or Plesk version).

Step 2: Add or Modify the MX Record

If you are switching to an external provider, you will likely need to delete existing MX records and create new ones. If you are configuring a local mail server, Plesk usually generates these automatically.

1. Inside the DNS Settings screen, click the Add Record button.
2. In the Record type dropdown menu, select MX.
3. Leave the Domain member or Domain field blank (or enter @ depending on the interface version) to apply it to your root domain (example.com).
4. In the Mail server field, enter the FQDN of your mail server (e.g., mail.example.com or your provider's target hostname).
5. In the Priority or Preference field, enter the integer assigned by your mail administrator (e.g., 10).
6. Click OK to save the record to the zone template.

Step 3: Update the Zone and Save Changes

After adding or editing the records, you will see a yellow notification bar at the top of the Plesk screen stating: "The DNS zone contains changes that have not been applied to the DNS server."

Click the Update button in that banner to publish the changes to the underlying BIND or NSD nameserver daemon.

Verifying Your DNS Configuration

Once updated, you need to verify that external mail servers can see your new settings. DNS propagation can take anywhere from a few minutes to a few hours depending on your TTL (Time to Live) settings.

You can query your domain's records from your terminal using command-line tools:

# Using dig to check MX records on Linux or macOS
dig example.com MX +noall +answer

Sample output:

example.com.		300	IN	MX	10 mail.example.com.

If you are on Windows, use PowerShell or nslookup:

# Using PowerShell to query MX records
Resolve-DnsName -Name example.com -Type MX

Sample output:

Name             Type   TTL   Section   NameExchange    Preference
----             ----   ---   -------   ------------    ----------
example.com      MX     300   Answer    mail.example.com          10

Common Mistakes and How to Fix Them

Even experienced administrators occasionally run into DNS pitfalls. Avoid these frequent errors:

• Pointing MX to an IP Address: An MX record must always point to a domain name (an A or AAAA record), never directly to an IPv4 or IPv6 address. Writing 192.0.2.10 in the mail server field will cause delivery to fail completely.
• Forgetting Associated A Records: If your MX record points to mail.example.com, you must ensure that a corresponding A record exists pointing mail.example.com to your server's public IP address (192.0.2.5).
• Leaving Conflicting Old Records: When migrating from local Plesk mail to an external provider, failing to delete the default local MX record creates a split-brain scenario where some emails land locally and others go externally.
• Mismatched Mail Server SSL/TLS: If your MX record points to mail.example.com, make sure that hostname is covered by a valid SSL/TLS certificate in Plesk (such as Let's Encrypt) to prevent email client security warnings.

Quick Checklist for Plesk Mail Setup

• Access Websites & Domains > DNS Settings in Plesk.
• Remove conflicting legacy MX records if migrating providers.
• Add the new MX record with the correct priority number.
• Ensure the target hostname has a valid A or AAAA record pointing to an IP address like 192.0.2.10.
• Click Update to commit changes to the DNS zone.
• Test propagation using command-line tools or online lookup utilities.