This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello
I have performed a cutover migration from on premise Exchange 2010 server in a Windows 2008 R2 domain, and also implemented DirSync. All works well.
In our local AD we have a slit brain DNS with a domain.local zone and a domain.com zone. I had to add a CNAME record with host name autodiscover pointing to autodiscover.outlook.com to get Outlook automatically find and configure itself to out new Office 365 Exchange environment.
It is the fact that I had to add this CNAME record in our local DNS that made me think, and now I have this question that I need an answer to:
In the migration process you have to add or change MX, CNAME, TXT and SRV records to your external DNS, so that your clients are able to reach services like Skype, MDM, SIP SRV. Shouldn't I also add/change those records to our local DNS zone domain.com? What about the MX record in our local DNS?
Microsoft 365 features that help users manage their subscriptions, account settings, and billing information.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
Hi Karlin,
To ensure the email delivering works fine, I recommend you delete the MX record of domain.local zone. About the domain.com zone, as I mentioned before, you can add all DNS records to your DNS server as well as the external network’s DNS records.
Best Regards,
Toby
Answer accepted by question author
Hi Karlin,
Yeah, I recommend you add those records including the MX record to your local DNS server.
Best Regards,
Toby
Next stop: I'm now trying to change MX record in my local DNS. The only MX-record present is located in my domain.local zone, and it has (same-as-parent) as hostname. Is it alright to change this record, or do I have to change this record somewhere else? Where or what is the "parent" to this record?
Thanks Toby!
I would like to suggest that this information is incorporated into the general guidance on how to make a cutover migration on eg this page: support.office.com/.../Perform-a-cutover-migration-of-email-to-Office