Questions about mxrecords (24 hours propagation period)
Good day,
If I change my MX record, i have to wait 24 hours approx before the DNDS cache is updated around the world...
. If someone tries to send me an email, while my mxrecord is still pointing to my old adress, what happens to the email? Will it bounce?
What if the a certain mail server Qqeue timeout is set to like 12 hours before sending an NDR?
Thanks.
If I change my MX record, i have to wait 24 hours approx before the DNDS cache is updated around the world...
. If someone tries to send me an email, while my mxrecord is still pointing to my old adress, what happens to the email? Will it bounce?
What if the a certain mail server Qqeue timeout is set to like 12 hours before sending an NDR?
Thanks.
will bounce back, ndr will only work if email gets to emails server
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Razmus,
You saying t hat If i change my TTL to 20 mins, there will be only 20 mins of downtime? I am planning to edith their Mx Record later this week.
I have 2 exchange servers, both are up. They are on different domains. (we acquired a small company)
I want to change their MXRecord to my mail server.
I have created the user accounts on my domain already, the email policy will be created so my domain will accept mails from their domain. (I added an smtp adress user@domain2.com on each user from the new branch in my domani1.com domain)
You saying t hat If i change my TTL to 20 mins, there will be only 20 mins of downtime? I am planning to edith their Mx Record later this week.
I have 2 exchange servers, both are up. They are on different domains. (we acquired a small company)
I want to change their MXRecord to my mail server.
I have created the user accounts on my domain already, the email policy will be created so my domain will accept mails from their domain. (I added an smtp adress user@domain2.com on each user from the new branch in my domani1.com domain)
ASKER
Last question,
I should change only their TTl right? Is there a need to change mine as well?
I should change only their TTl right? Is there a need to change mine as well?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
As of now, They have a WebHosting Company with mxrecords, nameservers and everything. Should i change the TTL there as well?
ASKER
I have checked my settings on my 2 exchange servers. Both are setup to 1 hour. However my Bluehost TTL is set to 14400 seconds and i cant change it to a lower value. Is that normal?
Both office have a Web Hosting contract and there are redirections made to their respective corporate IP for emails...
Both office have a Web Hosting contract and there are redirections made to their respective corporate IP for emails...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It will queue for a time, then bounce eventually, normally within a day.
Modifying the TTLs is a good approach, but not as safe as adding the new address to the MX prior to the change-over.
That is, if you were to add a new Host (A) record pointing at the new IP address (new mail server name) prior to the change, and add a secondary MX pointing to that name you would incur no downtime regardless of propagation.
Chris
The approach of adding a new MX host will only work if the old server is going to be decomissioned at move time. If it is still listening on port 25 then having the dual MX's is going to create confusion with multiple delivery locations.
As you own both of these servers, you have the ability to shut access to port 25 at cutover, so that would help, but then you have to go back to remove the old entry.
If your users are moving at the same time then you will have downtime for them anyway, so 10 mins downtime is fine.
If the servers are at the same location even better because you can reditrect traffic for server 1 to server 2 and then your MX records will ahve no affect at all. I assume they are not in the same IP ramges.
As you own both of these servers, you have the ability to shut access to port 25 at cutover, so that would help, but then you have to go back to remove the old entry.
If your users are moving at the same time then you will have downtime for them anyway, so 10 mins downtime is fine.
If the servers are at the same location even better because you can reditrect traffic for server 1 to server 2 and then your MX records will ahve no affect at all. I assume they are not in the same IP ramges.
ASKER
Last Question..
Does exmerge works with office 2007? Does it export contacts, address books etc as well?
Does exmerge works with office 2007? Does it export contacts, address books etc as well?
ExMerge is more of a server-side tool, only the version of Exchange matters. Typically you would use ExMerge for Exchange 2000 / 2003, and Export-Mailbox (Management Shell) for 2007 / 2010.
Don't forget that ExMerge has a 2Gb limit on PST files (old file format), worth bearing in mind if you have anyone with a particularly large mailbox. None of Outlook 2003 / 2007 / 2010 and Export-Mailbox suffer from that limitation (Outlook 2000 does).
Otherwise both tools export everything in the mailbox tree, Contacts, Calendar, Notes, etc, etc. If you're doing a full system move (one AD to another AD), I strongly urge you to export the LegacyExchangeDN values from the current domain, then import them as X500 addresses in the new domain. Only applies for cross-forest (different Exchange org) moves but without that you will have problems with replies to mails sent prior to the migration, and problems with ownership of calendar items.
Chris
ASKER
I have sucessfully rediorected the emails. Here is what I did..
Domain1.com
Domain2.com
A couple days before the redirection, (minimum of 24 hours) i have changed the TTL of domain2.com DNS management tool. i have changed it to 300 seconds. By default it is set at 24 hours most of the time.
48 hours later, I logged back in the dns management tool, and i changed the Mx Record to point to domain1.com ip hostname: mail.domain1.com
After that, I have created an email policy in Exchange system Manager, an i accepted the domain @domain2.com for all the new users account that i had already created on domain1.com Active Direcotry. (there was 8 new users)
Every thinig works perfect now.
Thanks to everyone. Its really apreciated.
Domain1.com
Domain2.com
A couple days before the redirection, (minimum of 24 hours) i have changed the TTL of domain2.com DNS management tool. i have changed it to 300 seconds. By default it is set at 24 hours most of the time.
48 hours later, I logged back in the dns management tool, and i changed the Mx Record to point to domain1.com ip hostname: mail.domain1.com
After that, I have created an email policy in Exchange system Manager, an i accepted the domain @domain2.com for all the new users account that i had already created on domain1.com Active Direcotry. (there was 8 new users)
Every thinig works perfect now.
Thanks to everyone. Its really apreciated.