Managing MX Records in DirectAdmin
Summary
This guide explains how to view and configure MX records in DirectAdmin. MX (Mail Exchanger) records determine where your domain receives e‑mail. If MX records are incorrect, e‑mail will not be delivered.
Overview
MX records control which mail server handles incoming messages for your domain. You can use your hosting server’s mail system or external providers such as Google Workspace or Microsoft 365. MX records must always point to hostnames, not IP addresses.
Requirements
- DirectAdmin user-level access
- DNS hosted on the same server or DNS control delegated to it
- Correct MX, SPF, DKIM, and DMARC records for reliable delivery
Step-by-Step Instructions
1. Access MX Records
- Log in to DirectAdmin
- Go to E‑mail Manager → MX Records
- Select the domain you want to manage
2. View Current MX Records
- The page displays all active MX entries
- Each entry includes:
• Priority
• Mail server hostname
3. Add a New MX Record
- Click “Add Record”
- Enter the mail server hostname (example: mail.yourdomain.com)
- Set the priority (lower number = higher priority)
- Save changes
4. Change MX Priority
- Find the MX record in the list
- Click “Edit”
- Adjust the priority value
- Save changes
5. Delete an MX Record
- Locate the MX entry
- Click “Delete”
- Confirm removal
Warning: Removing all MX records will stop all incoming e‑mail.
Common MX Configurations
Using Your Hosting Server (Default)
- Priority: 10
- Mail Server: mail.yourdomain.com
Google Workspace
- Priority 1: ASPMX.L.GOOGLE.COM
- Priority 5: ALT1.ASPMX.L.GOOGLE.COM
- Priority 5: ALT2.ASPMX.L.GOOGLE.COM
- Priority 10: ALT3.ASPMX.L.GOOGLE.COM
- Priority 10: ALT4.ASPMX.L.GOOGLE.COM
Microsoft 365
- Priority: 0
- Mail Server: yourdomain-com.mail.protection.outlook.com
Troubleshooting
E‑mail Not Arriving
- Ensure MX records point to the correct mail provider
- Check that MX records use hostnames, not IPs
- Verify DNS propagation (may take up to 24 hours)
Using External Mail but Still Receiving Local Mail
- Disable “Local Mail Server” in MX Records
- This prevents the server from trying to deliver mail locally
Mail Going to Spam
- Add SPF, DKIM, and DMARC records
- Ensure reverse DNS (PTR) is configured correctly
Multiple MX Records Causing Issues
- Ensure priorities are correct
- Remove outdated or unused MX entries
Related Articles
- [E‑mail Accounts](ca://s?q=Email_Accounts)
- [Forwarders](ca://s?q=Email_Forwarders)
- [SpamAssassin Setup](ca://s?q=SpamAssassin_Setup)
- [SPAM Filters](ca://s?q=SPAM_Filters)
- [E‑mail Tracking](ca://s?q=Email_Tracking)