MX record priority is a numbering system that dictates the order in which global mail servers attempt to deliver email to your domain. Mail servers always route messages to the record with the lowest priority number first. If the lowest-number server is offline, traffic automatically fails over to the next lowest number.
The Countdown Logic: Why Lower Numbers Win
MX priority works backward from what you might expect. The lowest number is the highest priority, not the highest number.
Think of it as a countdown, not a ranking. A record at priority 1 is contacted before a record at priority 10. If priority 1 doesn't respond, the sending server moves down the list until one accepts the message. This is the opposite of how most people intuitively read numbers, and it's the source of a lot of MX confusion.
Why It Matters: Building Reliable Failover
Undelivered email doesn't just vanish quietly. It either bounces back immediately or queues for retry over the following hours.
Correct priority ordering prevents:
- Lost customer inquiries and transactional emails
- Delayed delivery during a mail server outage
- Confusing bounce messages that damage sender trust
A well-configured priority chain keeps your domain receiving mail even during a brief primary server outage.
Decision Framework: Single Record vs Multi-Record Arrays
| | |
| Google Workspace: smtp.google.com at priority 1 | Simplicity, provider-managed redundancy |
| Titan Mail: mx1.titan.email (10), mx2.titan.email (20) | |
Google Workspace simplified its setup in 2023, moving from five ASPMX records to a single smtp.google.com record at priority 1. Redundancy is handled entirely on Google's end.
Multi-record providers like Titan Mail use a two-tier structure: primary at priority 10, secondary at priority 20. If the primary is unreachable, mail routes to the secondary automatically.
Follow whatever your provider documents rather than improvising your own setup.
Implementation Steps: Setting Priority Values at NameSilo
Step 1: Log into your NameSilo account and go to Domain Manager.
Step 2: Confirm your domain uses NameSilo's default nameservers (NS1/NS2/NS3.DNSOWL.COM), then click the blue globe icon next to your domain.
Step 3: Click "Add New DNS Record" and select type MX.
Step 4: Enter the mail server hostname exactly as your provider specifies (e.g., smtp.google.com or mx1.titan.email), then enter the priority number your provider requires. Use their documented value exactly; don't guess.
Step 5: For multi-record setups, repeat Step 3 for each additional server, giving it a higher (lower priority) number than the primary.
Step 6: Save and verify using MXToolbox to confirm records are live with correct priorities.
Common Mistakes
Giving two different providers the same priority: Setting Google Workspace and Titan Mail to the same priority splits incoming mail unpredictably between two separate inboxes. Some messages land in Gmail, others in Titan, with no reliable pattern.
Leaving old provider records active during a migration: Remove old MX records promptly when switching providers. A lingering low-priority record can keep intercepting mail even after adding the new provider's records.
Mixing single-record and multi-record configurations from the same provider: Never combine a provider's simplified option with their legacy multi-record set. This creates conflicting delivery instructions.
What This Means for You
Whether your email provider uses a single record or a multi-tier array, NameSilo Email integrates cleanly through DNS Manager. Priority values can be updated without disrupting live delivery, as changes only take effect once propagation completes. Frequently Asked Questions
What does priority mean in an MX record?
The order servers are tried; lower numbers go first.
Is a lower or higher MX priority number better?
Lower is better. Priority 1 is contacted before priority 10.
Can two MX records have the same priority?
Yes, but mail splits unpredictably. Avoid this across providers.
What happens if my primary MX server goes down?
Mail automatically routes to the next-lowest priority record.
What is a backup mail server?
A secondary MX record at a higher priority number for failover.
How do I set MX priority for Google Workspace?
Use a single record: smtp.google.com at priority 1.
Why is my email bouncing with an MX priority error?
Likely a leftover record from a previous provider conflicting.
How do I edit MX records at NameSilo?
DNS Manager, select MX type, enter host, value, and priority.