Hi,
I have recently migrated my website to a new host. Since migrating, inbound email through MS Office 365 is failing despite updating the Domain Zone settings in cpanel. 365 is reporting an error with MX and CNAME records. According to 365, the domain name seems to be appended to the end of the value, even though it hasn't in cpanel.
e.g., from the MX 365 health check:
Expected value: exampledomain-com-au01b.mail.protection.outlook.com
Actual value: exampledomain-com-au01b.mail.protection.outlook.com.exampledomain.com.au
and for CNAME:
Expected value: autodiscover.outlook.com
Actual value: autodiscover.outlook.com.exampledomain.com.au
I believe this is the same issue as reported here in the forum.
The expected values have been pasted in exactly as required by 365, yet it continues to report this problem. It happens with both the MX and CNAME but not the TXL value. So no email is getting through.
I have spoken to both the host provider and Microsoft, but not finding any solutions, so any help would be gratefully received.
I should also say my level of expertise in this area is next to zero, so hoping the solution might be simple!
Thanks,
Jamie
I have recently migrated my website to a new host. Since migrating, inbound email through MS Office 365 is failing despite updating the Domain Zone settings in cpanel. 365 is reporting an error with MX and CNAME records. According to 365, the domain name seems to be appended to the end of the value, even though it hasn't in cpanel.
e.g., from the MX 365 health check:
Expected value: exampledomain-com-au01b.mail.protection.outlook.com
Actual value: exampledomain-com-au01b.mail.protection.outlook.com.exampledomain.com.au
and for CNAME:
Expected value: autodiscover.outlook.com
Actual value: autodiscover.outlook.com.exampledomain.com.au
I believe this is the same issue as reported here in the forum.
The expected values have been pasted in exactly as required by 365, yet it continues to report this problem. It happens with both the MX and CNAME but not the TXL value. So no email is getting through.
I have spoken to both the host provider and Microsoft, but not finding any solutions, so any help would be gratefully received.
I should also say my level of expertise in this area is next to zero, so hoping the solution might be simple!
Thanks,
Jamie
Last edited: