How to Set Up a Backup MX Server for Email Redundancy
Learn how backup MX servers protect email delivery, how to configure primary and secondary MX records, and when you actually need email redundancy.
Email is one of the most mission-critical systems for any business. When it stops working, even for an hour, deals stall, customers go unanswered, and productivity drops. One of the simplest ways to add a safety net to your email delivery is through a backup MX server.
Most small businesses don't think about this until something breaks. This guide explains what a backup MX server is, how it works, when you actually need one, and how to set it up in a way that's appropriate for your business size.
What Is a Backup MX Server?
A backup MX server (also called a secondary MX server) is an alternative mail server that accepts incoming email when your primary mail server is unavailable.
Your domain's MX records define where incoming email should be delivered. When you have multiple MX records with different priority numbers, the internet's email system uses those priorities to decide which server to try first and which ones to fall back on if the first choice isn't responding.
If your primary mail server goes down for maintenance, experiences a network outage, or runs into a software issue, sending mail servers won't give up immediately. They'll look at your other MX records, find the backup server, and deliver there instead. Your recipients' messages get queued on the backup server until your primary comes back online, then they're forwarded along.
Think of it like having a backup voicemail box. If your main phone is off, calls go to the backup. When you turn your main phone back on, you retrieve those messages.
How MX Priority Creates Failover
Priority numbers are the key mechanism that makes failover work. Every MX record has a priority: a number that tells sending mail servers the preferred order for delivery attempts. Lower numbers are tried first.
Here's a simple example:
yourbusiness.com MX 10 mail.yourbusiness.com (primary)
yourbusiness.com MX 20 backup.yourbusiness.com (backup)
A sending mail server sees both records. It tries priority 10 first. If that server responds and accepts the message, delivery is done. If priority 10 is unreachable (no connection, timeout, server error), the sending server moves on and tries priority 20.
The sending server doesn't give up immediately; it tries for several seconds to connect to each MX host before moving to the next priority level. If all MX servers are temporarily unavailable, the sending mail server will queue the message and retry delivery at intervals over the next 72 hours or so.
This means even a complete outage of your primary mail server doesn't necessarily mean lost email, as long as your backup is up and eventually your primary recovers.
When You Actually Need a Backup MX
Here's an honest answer. Many small businesses using a major email provider like Google Workspace or Microsoft 365 don't need to set up their own backup MX server.
Google and Microsoft already operate their mail infrastructure with massive built-in redundancy. When you add Google Workspace MX records, you're adding five of them at two different priority levels. Google's systems handle the failover internally. The same is true for Microsoft 365, Zoho, and most large email service providers.
Where backup MX becomes genuinely important is when:
- You run your own mail server. If you host email on a server you control, a single point of failure exists. A hardware failure, ISP outage, or power event at your location can stop email dead. A backup MX at a different location keeps delivery going.
- You use a smaller or regional email hosting provider that runs limited infrastructure. Less redundancy in the provider means more value in having your own backup.
- Email reliability is business-critical. Law firms, medical practices, financial services companies, and others where a missed email has real consequences often want extra protection.
- You have a compliance requirement that mandates you demonstrate resilience planning for communication systems.
If you're a 5-person business on Google Workspace, you probably don't need a backup MX. If you're running your own Postfix server on a VPS, you probably do.
How to Configure Primary and Backup MX Records
Setting up MX failover is straightforward: you add two (or more) MX records with different priority values.
Step 1: Identify your backup mail server. This could be a second server you control, a backup MX service you subscribe to (more on that below), or a server your email provider designates.
Step 2: Log into your DNS management panel (your domain registrar or DNS host).
Step 3: Add your MX records. You need at least two:
Name: @ Mail Server: mail.yourdomain.com Priority: 10
Name: @ Mail Server: backup-mail.yourdomain.com Priority: 20
The exact priority numbers don't matter as long as the backup has a higher number (lower priority) than the primary. You can use 10/20, 1/10, or 5/50; the relative order is what counts.
Step 4: Verify with the MX checker. Go to mxrecordchecker.com and enter your domain. Confirm both MX records appear with the correct priorities. The tool makes it easy to see your complete MX configuration at a glance.
Third-Party Backup MX Services
If you run your own mail server but don't have the resources to set up and maintain a second one, third-party backup MX services are an affordable option.
These services act as your secondary MX server. When your primary server is down, they accept incoming messages and queue them. When your primary comes back up, they forward the queued messages along. You typically pay a small monthly fee based on the number of domains or messages handled.
Some well-known providers in this space include MXroute, MX Backup, and various managed hosting providers that offer secondary MX as an add-on. When evaluating these services, look for:
- Geographic separation from your primary server (no point in a backup that shares your ISP or data center)
- Queue duration: how long will they hold messages if your primary is down?
- Delivery notifications: will they alert you when they're holding queued mail?
- Spam filtering: some backup MX services will queue spam too, leading to a flood when your primary recovers
Testing Failover with the MX Checker
Once you've set up backup MX records, you should test that the failover actually works. Don't wait for a real outage to find out.
The first test is simple: check that both records appear correctly. Go to mxrecordchecker.com, enter your domain, and confirm you see both your primary and backup MX records with the right priorities.
The deeper test involves temporarily making your primary server unavailable (or blocking port 25 on it in your firewall) and sending yourself a test email. If your backup is configured correctly, the message should arrive, though it may be held for several minutes while the sending server retries the primary before falling back.
For businesses where email reliability is critical, run this test before you need it, not during an actual emergency.
Risks and Downsides of Backup MX
A backup MX server isn't purely upside. There are some well-known downsides to be aware of:
Spam relay. Spammers know that backup MX servers often have less aggressive spam filtering than primary servers. They deliberately target backup MX servers hoping to get messages delivered that the primary would reject. If your backup MX doesn't have robust spam filtering, you may end up delivering junk that your primary would have blocked.
Queuing delays. Messages queued on a backup server don't get delivered to your primary until it comes back up. If your primary is down for 6 hours, messages that arrived at the backup are delivered 6 hours late. For most businesses this is acceptable, but if you're expecting time-sensitive messages during an outage, be aware they won't arrive instantly when you're back.
Configuration complexity. A backup MX server needs to be configured correctly to forward to your primary, which adds an additional moving part to your email infrastructure. Misconfigured backup servers can cause mail loops or delivery failures.
False sense of security. Having a backup MX doesn't mean your email infrastructure is rock-solid. If your primary has been down long enough that the backup's queue is filling up, or if there's a more fundamental problem with your domain or DNS, a backup MX may not help.
Best Practices for Backup MX Setup
Keep these principles in mind when setting up email redundancy:
Use meaningful priority spacing. A gap of at least 10 between primary and backup priorities (e.g., 10 and 20) gives room to add intermediate servers later without renumbering.
Locate the backup separately. Your backup MX server should be in a different physical location, on a different network, and ideally with a different provider. A backup on the same server as your primary is no backup at all.
Apply spam filtering on the backup. Don't let your backup accept everything without filtering. Configure it to apply at least basic spam and malware checks.
Monitor both servers. Set up monitoring so you know when your primary goes down and how long the backup has been absorbing traffic. The faster you know about an outage, the faster you can fix it.
Verify your configuration regularly. Run a quick check at mxrecordchecker.com every few months to confirm your MX records still look right, since they can get accidentally changed during unrelated DNS work.
Email redundancy is worth the investment for any business that relies on it to operate. The setup is not complicated, and the peace of mind it provides is genuine.