Hi Friends,

I want to know that it is possible to avoid mail loss during MX Records and other DNS Records Because it takes 24 Hrs. to update.

As a best practice, you should

1. Shorten the TTL of related DNS records (MX, A, CNAME etc) before the actual update. For example, change the TTL to 1 hour at least 24 hours before the actual update time. You can set it back after the update.

2. Keep the old SMTP host running. For example, if you have set TTL to 1 hour, your old SMTP host should be up and running for at least 1 hour after the DNS update.

Thanks for reply :)

I am unable to understand. Can you please share any link or article related this.

Which part you can;t understand? Is it TTL? You may do a Google search "DNS TTL" or "DNS record time to live".

As a best practice, you should

1. Shorten the TTL of related DNS records (MX, A, CNAME etc) before the actual update. For example, change the TTL to 1 hour at least 24 hours before the actual update time. You can set it back after the update.

2. Keep the old SMTP host running. For example, if you have set TTL to 1 hour, your old SMTP host should be up and running for at least 1 hour after the DNS update.

• Proposed as answer by JasonAptMicrosoft community contributor 11 hours 8 minutes ago

As a best practice, you should

1. Shorten the TTL of related DNS records (MX, A, CNAME etc) before the actual update. For example, change the TTL to 1 hour at least 24 hours before the actual update time. You can set it back after the update.

2. Keep the old SMTP host running. For example, if you have set TTL to 1 hour, your old SMTP host should be up and running for at least 1 hour after the DNS update.

• Proposed as answer by JasonAptMicrosoft community contributor Thursday, May 28, 2015 8:19 PM
• Marked as answer by Online24x7 21 hours 29 minutes ago

As a best practice, you should

1. Shorten the TTL of related DNS records (MX, A, CNAME etc) before the actual update. For example, change the TTL to 1 hour at least 24 hours before the actual update time. You can set it back after the update.

2. Keep the old SMTP host running. For example, if you have set TTL to 1 hour, your old SMTP host should be up and running for at least 1 hour after the DNS update.

• Proposed as answer by JasonAptMicrosoft community contributor Thursday, May 28, 2015 8:19 PM
• Marked as answer by Online24x7 Friday, May 29, 2015 9:57 AM

Hi,

I want to migrate from google apps to Microsoft exchange server 2013 on-premise and want to prevent mail loss during DNS Records Update.

is it possible to prevent mail loss?

• Edited by Online24x7 8 minutes ago

Hi,

As Li mentioned, we also increase the Exchange 2013 connection limits to your IMAP server (Gmail limits it to 15 simultaneous connections), shortening the DNS Time-to-Live setting on your MX record, and backing up and deleting any filters set up in Google Apps.
The first step is to create the mailboxes in Exchange 2013, which you can do one at a time or in bulk using a CSV file. You also need to assign licenses to each user for Exchange 2013. At this point, you probably want to switch the DNS MX records from Google Apps to Exchange 2013, so no email is lost in the switch.

Heres an article about migration performance and best practices, for your reference: https://technet.microsoft.com/en-us/library/dn592150%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

Thanks

Thanks  

:)

But this article is related to Exchange Online Migration but i want to go for On-Premise.

Hi,

I want to migrate from google apps to Microsoft exchange server 2013 on-premise and want to prevent mail loss during DNS Records Update.

is it possible to prevent mail loss?

• Edited by Online24x7 Friday, May 29, 2015 7:20 AM