AXISHK
asked on
Exchange cloud
During the inital DNS setup on Exchange cloud, it need to create the MX, CNAME , TXT and SRV.
As we will only migrate the domain after few weeks later, should I only add CNAME, TXT and SRV and leave MX remain unchanged until the migration day ? Will it affect my current mail flow by only adding /changing CNAME, TXT and SRV ? Can I test the account in Cloud within the MX record change ?
Current, there is one MX record , with priority 0 pointing to my Exchange on premise server. Should I set the MS to higher priority (say 5) and swap the sequence on the migration day ?
Thx
As we will only migrate the domain after few weeks later, should I only add CNAME, TXT and SRV and leave MX remain unchanged until the migration day ? Will it affect my current mail flow by only adding /changing CNAME, TXT and SRV ? Can I test the account in Cloud within the MX record change ?
Current, there is one MX record , with priority 0 pointing to my Exchange on premise server. Should I set the MS to higher priority (say 5) and swap the sequence on the migration day ?
Thx
ASKER
But without those MX, CNAME , TXT and SRV, can I still setup the Outlook profile to test the Exchange Cloud connectivity ?
Or, should I simply add CNAME. TXT and SRV and let MX remain unchanged until the migration ?
Thx
Or, should I simply add CNAME. TXT and SRV and let MX remain unchanged until the migration ?
Thx
the issue is CNAME is a canonical name record which called as well as Alias Record
SRV Service record is related to the services...
the issues is while you create DNS records on cloud/office 365 the Alias record which is actual Cloud/Office 365 record's Alias record will be created for your domain name the same thing happens with service records.
while the existing mail server receives mails from out side when external servers search for your domain DNS records they'll find additional alias record on office 365 as well which points to other ip.. which can make issues ... can point to blacklist your domain etc.
so the best practice is just create TXT record on your present DNS and verify the domain keep them ready for migration...
when ever you want to migrate simply create cname, srv, Mx and one more txt record.
thats it.
all the best
SRV Service record is related to the services...
the issues is while you create DNS records on cloud/office 365 the Alias record which is actual Cloud/Office 365 record's Alias record will be created for your domain name the same thing happens with service records.
while the existing mail server receives mails from out side when external servers search for your domain DNS records they'll find additional alias record on office 365 as well which points to other ip.. which can make issues ... can point to blacklist your domain etc.
so the best practice is just create TXT record on your present DNS and verify the domain keep them ready for migration...
when ever you want to migrate simply create cname, srv, Mx and one more txt record.
thats it.
all the best
ASKER
Can I manually setup the Outlook profile with only TXT record added to my present DNS ?
Which setting should I setup for Microsoft Exchange server, Microsoft Exchange Proxy Settings ?
Thx
Which setting should I setup for Microsoft Exchange server, Microsoft Exchange Proxy Settings ?
Thx
the TXT record is to verify your DNS ownership verification only nothing else...
actually when you create account on office 365 there you can create you company domain name which will appears like
yourdomain.onmicrosoft.com
with this name you can create email id's and configure them as well on outlook as well and test the mail flow which will works without any issue.
but the thing is when you change MX point direct to your domain.com then you have to create and test all DNS records.
all the above comments are assuming you have a running mail server which you want to migrate to office 365/cloud solution. and you don't want to make conflict while migration.
thanks
actually when you create account on office 365 there you can create you company domain name which will appears like
yourdomain.onmicrosoft.com
with this name you can create email id's and configure them as well on outlook as well and test the mail flow which will works without any issue.
but the thing is when you change MX point direct to your domain.com then you have to create and test all DNS records.
all the above comments are assuming you have a running mail server which you want to migrate to office 365/cloud solution. and you don't want to make conflict while migration.
thanks
ASKER
yes, i have exchange 2003 server and want to migrate to cloud.
so, the user will be setup as john@mycompany.onmicrosoft
During the migration, I will change the MX, TXT, CNAME,... and change the user from john@mycompany.onmicrosoft
Is there a better way to handle the migration ? Actually, I want the Exchange cloud profile be ready on each workstation. Once the migration is done, users can simply select the new Outlook profile. Any comment.
Thx again.
so, the user will be setup as john@mycompany.onmicrosoft
During the migration, I will change the MX, TXT, CNAME,... and change the user from john@mycompany.onmicrosoft
Is there a better way to handle the migration ? Actually, I want the Exchange cloud profile be ready on each workstation. Once the migration is done, users can simply select the new Outlook profile. Any comment.
Thx again.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thx
the mx with highest priority is not recommended ... on different setups.
all the best