MX records route inbound email for a domain to mail-server hostnames in priority order.
Applies to: Nameservers and DNS records
DNS tells internet services where to find a website, mail server or other service. Changes can be technically correct yet appear inconsistent for a time because recursive resolvers cache earlier answers until their TTL expires.
Before you start
- Have the complete MX hostnames and priorities from the email provider.
- Confirm whether old and new mail systems must coexist during migration.
Step-by-step
- Remove or retain existing MX records only according to the migration plan; an unplanned mixture can send different messages to different providers.
- Create each MX record at the correct domain name and enter the provider hostname, not an IP address.
- Set the numeric priorities exactly as supplied. Lower numbers are normally preferred, but priority does not create load balancing or mailbox synchronisation.
- Add any required SPF, DKIM, DMARC and verification records separately.
- Query the authoritative nameservers and send test messages from at least two external providers.
- Keep the old mail service available until cached MX answers and migration work are complete.
Confirm the result
- External senders resolve the intended MX set and messages arrive in the correct destination mailbox.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| Mail arrives at both old and new systems. | Cached records or a mixed MX set remains active. | Keep both systems monitored, correct the authoritative records and wait for previous TTLs. |
| The DNS panel asks for a host but the provider supplied an IP. | MX records require a hostname with its own A or AAAA record. | Ask the provider for the supported MX hostname rather than inventing one. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The full domain name
- The current and intended registrar or nameservers
- Any registry or transfer error shown
- Whether website or email service is currently live
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- A, AAAA, CNAME, MX and TXT records explained
- Use different providers for website and email hosting
- Set up SPF, DKIM and DMARC records
- Troubleshoot hosting email sending and delivery
- Create and troubleshoot TXT records
Last reviewed: 2026-07-18.
