Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Email & DNS

MX priority explained: how mail servers choose where to deliver

Published August 2026 · 2 min read · Updated 2026-09-05

MX priority is a preference number used when a sending mail server chooses among MX hosts. Lower numbers are preferred, but priority does not create replication, mailbox synchronization, or automatic failover correctness. Every advertised MX must be able to handle mail for the domain as intended.

Read the complete MX set

Query authoritative DNS and record every MX hostname and preference. Resolve each hostname to its addresses and verify it is the service you expect.

A stale secondary MX can accept or reject mail differently from the primary and become a hidden delivery problem during outages.

Understand equal and unequal preference

Senders normally try lower-preference values first; equal-priority MX records can distribute attempts. Exact retry behavior is sender-specific, so do not assume deterministic load balancing.

A backup MX with a higher number still needs a secure path to deliver accepted messages onward.

Keep MX hostnames as hostnames

MX records point to names, not IP addresses. Those names should resolve to A/AAAA data appropriate for SMTP. Avoid CNAMEs at MX targets because standards and receiving implementations expect mail exchanger hostnames directly.

Coordinate reverse DNS and TLS identity on the actual sending/receiving servers separately.

Test from outside

Send representative external mail, verify which MX accepted it, inspect SMTP/TLS logs, and confirm final mailbox delivery. Remove old MX records only after their traffic has ceased.

  • Inventory the whole MX set.
  • Lower number means higher preference.
  • Ensure every MX can process mail safely.
  • Test real delivery, not DNS alone.

Next step

Understand MX preference values, fallback hosts and equal-priority records, then verify the selected mail servers actually accept mail for the domain.

Explore DotMoose domains and DNS

Keep reading

Related guides.

CAA record planning: control which certificate authorities may issue for a domain

Plan CAA records around the certificate providers you use, subdomains and incident contacts, then verify issuance will still work before enforcing restrictions.

Read the guide

CNAME chain problems: why extra DNS aliases can break or slow resolution

Trace CNAME chains, loops, missing terminal records and provider restrictions, then shorten unnecessary aliases without changing the intended hostname.

Read the guide

DKIM selector rotation: change signing keys without breaking verification

Rotate DKIM selectors by publishing the new key first, switching signers, monitoring authentication and retaining the old selector long enough for queued mail.

Read the guide

More domains & dns guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move