MX Records Explained: Why Your Business Emails Are Not Arriving
Are your business emails not arriving? Perhaps you recently moved your website to another hosting provider, switched to Microsoft 365 or Google Workspace, or created a new email account that cannot receive messages.
One possible cause is an incorrect **MX record** in your domain's DNS settings. However, email delivery also depends on mailbox configuration, server availability and security policies.
This guide explains how MX records work and how to troubleshoot email delivery problems.
## What Is an MX Record?
MX stands for **Mail Exchange**. An MX record tells sending email servers which mail servers are responsible for receiving email for a domain.
For example, when someone sends an email to `info@example.com`, the sending server looks up the MX records for `example.com` to determine where the message should be delivered.
An MX record can contain a mail server hostname and a priority value.
For example:
- Priority 10: `mail1.example.net`
- Priority 20: `mail2.example.net`
The lower preference number generally indicates the preferred server.
These hostnames are examples, not actual settings you should copy into your domain.
## 1. Incorrect MX Records
One of the most common email configuration mistakes is pointing MX records to an old or incorrect mail server.
For example, if your business migrates from cPanel email to Microsoft 365 but leaves the old MX records active, incoming emails may still be directed to the previous hosting provider.
**What to do:**
1. Open [IPZW DNS Lookup](https://whatismyipaddress.co.zw/dns-lookup).
2. Enter your domain name.
3. Select the MX record type.
4. Compare the result with your email provider's official configuration.
If the records are incorrect, update them at your active DNS provider.
## 2. DNS Changes and Caching
When you update an MX record, some DNS resolvers may continue returning the previous value until its cache expires.
This can cause temporary inconsistencies during an email migration.
Check your authoritative DNS settings and allow time for cached records to expire. Avoid repeatedly changing the records while troubleshooting.
## 3. Wrong Name Servers
A common mistake is editing DNS records in the wrong location.
For example, your website may be hosted in cPanel while your domain uses Cloudflare name servers.
In that case, changing MX records inside cPanel might not affect the public DNS configuration.
Check which name servers are authoritative for your domain and make your changes through the appropriate DNS provider.
## 4. Incorrect Email Routing in cPanel
cPanel provides email-routing settings that determine how the hosting server handles messages for a domain.
Common options include:
- Local Mail Exchanger
- Remote Mail Exchanger
- Backup Mail Exchanger
- Automatically Detect Configuration
If your website is hosted in cPanel but your email is hosted externally, **Remote Mail Exchanger** is often appropriate.
However, the correct selection depends on your setup. Confirm where email should be delivered before changing the setting.
## 5. Microsoft 365 Email Problems
When using Microsoft 365 with a custom domain, your MX record must match the domain-specific value provided in the Microsoft 365 admin center.
Common mistakes include:
- Using an incorrect MX hostname.
- Leaving old mail-provider MX records in place.
- Updating DNS at the wrong provider.
- Configuring DNS before the necessary mailboxes are ready.
Check the domain setup in your Microsoft 365 admin center and compare it with the publicly available MX records.
Remember that changing MX records does not automatically migrate messages from your previous provider.
## 6. Google Workspace Email Problems
Google Workspace also requires appropriate MX records for incoming email.
If your business moves from cPanel or another mail provider, confirm that your domain's MX settings match Google's current instructions.
You should also verify that the domain and user mailboxes are configured correctly in the Google Admin console.
Avoid copying MX values from unrelated websites; use the instructions provided for your Workspace configuration.
## 7. SPF, DKIM and DMARC
MX records direct incoming email, while SPF, DKIM and DMARC help receiving systems assess email authentication.
**SPF:** Identifies which mail servers are authorized to send email for your domain.
**DKIM:** Uses cryptographic signatures to help verify that an email was authorized and has not been altered in transit.
**DMARC:** Defines a policy based on SPF and DKIM authentication and alignment, and can provide reporting about authentication results.
Incorrect SPF, DKIM or DMARC configurations can contribute to outgoing messages being rejected or treated as suspicious.
If you cannot receive emails, investigate MX records, mailbox status and receiving-server logs first.
## 8. Other Reasons Emails May Not Arrive
Not every email issue is caused by DNS.
Other possible causes include:
- A full or disabled mailbox.
- An incorrect recipient address.
- Messages being moved to spam or quarantine.
- Email forwarding or inbox rules.
- Temporary mail server problems.
- Security policies blocking incoming messages.
If possible, examine the bounce message or email delivery log to determine whether the message was rejected, deferred or accepted.
## How to Check Your MX Records
You can use IPZW Network Tools to inspect your domain's public DNS records.
1. Visit [IPZW DNS Lookup](https://whatismyipaddress.co.zw/dns-lookup).
2. Enter the domain you want to investigate.
3. Select **MX** from the record-type dropdown.
4. Run the lookup.
5. Compare the returned mail servers with your provider's official settings.
A correct MX record is important, but it does not guarantee that email delivery will succeed.
## Frequently Asked Questions
### Why can I send emails but not receive them?
This can happen when MX records point to the wrong server, the recipient mailbox is unavailable, or incoming messages are blocked or redirected.
### Can I host my website in cPanel and use Microsoft 365 for email?
Yes. Website hosting and email hosting can use different providers as long as DNS and email routing are configured correctly.
### Will changing MX records delete my existing emails?
No. Changing MX records does not directly delete stored messages. However, it does not migrate old mailboxes either.
### How long do MX record changes take?
The time depends on DNS caching and TTL settings. Different resolvers may temporarily return different values.
### Do SPF, DKIM and DMARC replace MX records?
No. They support email authentication, while MX records identify the servers responsible for receiving incoming email.
## Conclusion
If your business emails are not arriving, start by checking the domain's MX records, authoritative name servers, email-routing settings and mailbox status.
Use [IPZW DNS Lookup](https://whatismyipaddress.co.zw/dns-lookup) to inspect your DNS configuration and identify possible problems.
For more free networking utilities and troubleshooting guides, visit [IPZW Network Tools](https://whatismyipaddress.co.zw/).
One possible cause is an incorrect **MX record** in your domain's DNS settings. However, email delivery also depends on mailbox configuration, server availability and security policies.
This guide explains how MX records work and how to troubleshoot email delivery problems.
## What Is an MX Record?
MX stands for **Mail Exchange**. An MX record tells sending email servers which mail servers are responsible for receiving email for a domain.
For example, when someone sends an email to `info@example.com`, the sending server looks up the MX records for `example.com` to determine where the message should be delivered.
An MX record can contain a mail server hostname and a priority value.
For example:
- Priority 10: `mail1.example.net`
- Priority 20: `mail2.example.net`
The lower preference number generally indicates the preferred server.
These hostnames are examples, not actual settings you should copy into your domain.
## 1. Incorrect MX Records
One of the most common email configuration mistakes is pointing MX records to an old or incorrect mail server.
For example, if your business migrates from cPanel email to Microsoft 365 but leaves the old MX records active, incoming emails may still be directed to the previous hosting provider.
**What to do:**
1. Open [IPZW DNS Lookup](https://whatismyipaddress.co.zw/dns-lookup).
2. Enter your domain name.
3. Select the MX record type.
4. Compare the result with your email provider's official configuration.
If the records are incorrect, update them at your active DNS provider.
## 2. DNS Changes and Caching
When you update an MX record, some DNS resolvers may continue returning the previous value until its cache expires.
This can cause temporary inconsistencies during an email migration.
Check your authoritative DNS settings and allow time for cached records to expire. Avoid repeatedly changing the records while troubleshooting.
## 3. Wrong Name Servers
A common mistake is editing DNS records in the wrong location.
For example, your website may be hosted in cPanel while your domain uses Cloudflare name servers.
In that case, changing MX records inside cPanel might not affect the public DNS configuration.
Check which name servers are authoritative for your domain and make your changes through the appropriate DNS provider.
## 4. Incorrect Email Routing in cPanel
cPanel provides email-routing settings that determine how the hosting server handles messages for a domain.
Common options include:
- Local Mail Exchanger
- Remote Mail Exchanger
- Backup Mail Exchanger
- Automatically Detect Configuration
If your website is hosted in cPanel but your email is hosted externally, **Remote Mail Exchanger** is often appropriate.
However, the correct selection depends on your setup. Confirm where email should be delivered before changing the setting.
## 5. Microsoft 365 Email Problems
When using Microsoft 365 with a custom domain, your MX record must match the domain-specific value provided in the Microsoft 365 admin center.
Common mistakes include:
- Using an incorrect MX hostname.
- Leaving old mail-provider MX records in place.
- Updating DNS at the wrong provider.
- Configuring DNS before the necessary mailboxes are ready.
Check the domain setup in your Microsoft 365 admin center and compare it with the publicly available MX records.
Remember that changing MX records does not automatically migrate messages from your previous provider.
## 6. Google Workspace Email Problems
Google Workspace also requires appropriate MX records for incoming email.
If your business moves from cPanel or another mail provider, confirm that your domain's MX settings match Google's current instructions.
You should also verify that the domain and user mailboxes are configured correctly in the Google Admin console.
Avoid copying MX values from unrelated websites; use the instructions provided for your Workspace configuration.
## 7. SPF, DKIM and DMARC
MX records direct incoming email, while SPF, DKIM and DMARC help receiving systems assess email authentication.
**SPF:** Identifies which mail servers are authorized to send email for your domain.
**DKIM:** Uses cryptographic signatures to help verify that an email was authorized and has not been altered in transit.
**DMARC:** Defines a policy based on SPF and DKIM authentication and alignment, and can provide reporting about authentication results.
Incorrect SPF, DKIM or DMARC configurations can contribute to outgoing messages being rejected or treated as suspicious.
If you cannot receive emails, investigate MX records, mailbox status and receiving-server logs first.
## 8. Other Reasons Emails May Not Arrive
Not every email issue is caused by DNS.
Other possible causes include:
- A full or disabled mailbox.
- An incorrect recipient address.
- Messages being moved to spam or quarantine.
- Email forwarding or inbox rules.
- Temporary mail server problems.
- Security policies blocking incoming messages.
If possible, examine the bounce message or email delivery log to determine whether the message was rejected, deferred or accepted.
## How to Check Your MX Records
You can use IPZW Network Tools to inspect your domain's public DNS records.
1. Visit [IPZW DNS Lookup](https://whatismyipaddress.co.zw/dns-lookup).
2. Enter the domain you want to investigate.
3. Select **MX** from the record-type dropdown.
4. Run the lookup.
5. Compare the returned mail servers with your provider's official settings.
A correct MX record is important, but it does not guarantee that email delivery will succeed.
## Frequently Asked Questions
### Why can I send emails but not receive them?
This can happen when MX records point to the wrong server, the recipient mailbox is unavailable, or incoming messages are blocked or redirected.
### Can I host my website in cPanel and use Microsoft 365 for email?
Yes. Website hosting and email hosting can use different providers as long as DNS and email routing are configured correctly.
### Will changing MX records delete my existing emails?
No. Changing MX records does not directly delete stored messages. However, it does not migrate old mailboxes either.
### How long do MX record changes take?
The time depends on DNS caching and TTL settings. Different resolvers may temporarily return different values.
### Do SPF, DKIM and DMARC replace MX records?
No. They support email authentication, while MX records identify the servers responsible for receiving incoming email.
## Conclusion
If your business emails are not arriving, start by checking the domain's MX records, authoritative name servers, email-routing settings and mailbox status.
Use [IPZW DNS Lookup](https://whatismyipaddress.co.zw/dns-lookup) to inspect your DNS configuration and identify possible problems.
For more free networking utilities and troubleshooting guides, visit [IPZW Network Tools](https://whatismyipaddress.co.zw/).