The Necessity of Redundancy
Email is the lifeblood of modern business. A downed mail server doesn’t just mean delayed messages; it can mean lost revenue, missed critical alerts, and significant reputational damage. Therefore, relying on a single mail server represents a severe single point of failure. High Availability (HA) email architecture is designed to prevent this, and at the DNS level, it is entirely managed through the strategic configuration of multiple MX records and their priority values.
Primary and Backup Configurations
The most common HA setup involves designating a primary mail gateway and one or more backup gateways. For example, you might configure mx1.example.com with a priority of 10, and mx2.example.com with a priority of 50. Under normal circumstances, all sending servers worldwide will respect the lowest number and route traffic exclusively to mx1. If mx1 experiences a hardware failure, network outage, or is taken offline for maintenance, sending servers will automatically attempt to connect to the next highest priority: mx2. The backup server queues the incoming mail and periodically attempts to deliver it to the primary server once it comes back online.
Load Balancing via Equal Priorities
MX records can also be used for rudimentary load balancing. If you assign the exact same priority value to multiple MX records (e.g., both mx-a.example.com and mx-b.example.com are set to priority 10), sending MTAs will distribute their connections randomly across the available servers. This is an effective way to distribute massive volumes of incoming mail across a cluster of spam filters or Exchange Edge Transport servers without needing a dedicated hardware load balancer.
The Risks of Open Relays in Backup Servers
When designing a backup MX architecture, security must be a top consideration. A common historical vulnerability involved poorly configured backup mail servers that acted as ‘open relays.’ Spammers would deliberately target the backup MX server (e.g., the priority 50 server), knowing it often had less stringent spam filtering than the primary gateway. Today, it is imperative that all servers listed in your MX configuration enforce the same rigorous anti-spam, SPF, DKIM, and DMARC checks. Before finalizing your architecture, verify that your priority routing is correctly published to the world using an advanced DNS Lookup tool.
