Email server redundancy

I finally installed Exchange 2010 on my network.
However, I don’t fully trust my setup so I did not move my company’s emails to it. I’ve set up as the domain for Exchange.’s emails are hosted with an external ISP.

1. How do I move now’s emails to Exchange?
Is this as simple as?
•      Adding as Accepted Domain to Exchange’s Organization Configuration | Hub Transport
•      Pointing’s MX record to Exchange

 2. If I want to go back to my ISP, I just have to re-point my’s MX record to the ISP’s email server?
More, than that, can I switch back and forth between hosting my emails on my Exchange or hosting them by my ISP, with having only the ‘penalty’ of propagating the MX record’s IP (10-20hour delay, that I can afford in the weekends)?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jesse BSystem AdministratorCommented:
If the reason for the switching back between your exchange server and ISP's mail server is to provide redundancy, you may be better off having two MX records.  The higher priority MX record pointing to your Exchange server and the second record pointing to the ISP.  THat way if your Exchange server is unavailable, the email should go to the ISP.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mihaiszAuthor Commented:
Thaks for the quick response.
How about switching to Exchange from the ISP, in case I don't want to use the ISP any more. Is it as described at #1?
#1: yes that's all you should have to do to get mail delivered to your server instead of your ISPs.

You can actually cut down that propagation time dramatically by tweaking your TTL (time to live) values in DNS. Usually by default they're set to 86400 seconds (1 day), but you can set them to 300 seconds (5 minutes) or less if you have control over your DNS. If you set the value very low you'll only have to wait that amount of time before the changes are seen globally.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Servers

From novice to tech pro — start learning today.