Previously our domain, let's call it ourdomain.com, pointed to an IP address (our web host). In addition, we use Office 365 to handle our domain email accounts. DNS records:
ourdomain.com A XXX.XXX.XXX.XXX
ourdomain.com MX 10 our-domain.protection.mail.outlook.com
Now we have moved to Azure's cloud environment. It is recommended to not use A records and rather CNAME records, as IP addresses are not guaranteed to be retained.
So we removed the A record and added the CNAME:
ourdomain.com CNAME ourcloudsite.cloudapp.net
ourdomain.com MX 10 our-domain.protection.mail.outlook.com
Now our email is not being received. The result of an nslookup for MX records on ourdomain.com is also incorrect.
I've read that we need to have an A record for MX records to resolve. What A record are we supposed to use then?
We could use the IP of ourcloudsite.cloudapp.net, but then we risk having downtime.
example.com
). This will be breaking everything else. See lots of posts on SF to that effect, such as serverfault.com/questions/494473/… . – MadHatter May 18 '14 at 11:57CNAME
works in combination with the lack ofSRV
support for http/https in web browsers is certainly a factor. (As for what constitutes "a decent understanding", this can obviously be debated. One could argue that understanding theCNAME
record type would be included.) – Håkan Lindqvist May 18 '14 at 13:10CNAME
record. I would go as far as saying that a lot of common "knowledge" regarding the record type is incorrect. Example: The very first sentence of the Wikipedia article on CNAME records gets it wrong in a way that will lead the reader, should they base their reasoning on an explanation along those lines, down a path where things like this issue will make little or no sense. – Håkan Lindqvist May 18 '14 at 15:05