domainx.local for Active directory, for web and e-mail. How manage mx record with local exchange?

Hello people,
situation is:

local ad 2003 server domainx.local
local exchange 2003 with internal domainx.local
web space and about 60 e-mail given by Ips,
two outlook account on pc clients

I'm trying to understand how resolve this incredible situation.
I would set mx record pointing to local exchange, having a "real" email solution (managing delegates, scheduled archive, centralized sign, BES server) but i'm really sad....i'm forced to setting up a new local domain first? Sure i cannot loose 60 email....
1) i have to reinstall domain, and re-add 7 servers and 70 client? =:-(
Only then, set the mx record...and go on
2) can i resolve by a good 3rd party Pop3 connector, managing the duplicated account for 1 user? I have to renounce any features?
3) can i first migrate actual domain to the new one (file user rights....share...groups...). I think i cannot simply rename...

Can u help finding the right way?
Sorry for my english, ask me for details....sure i forgetting elements.
Really thanks

Mattia MinerviniAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

You don't need to make an internal MX record to route email.  The clients will connect directly with the exchange server.  You should have one MX record at whoever's hosting your public DNS pointing to the public interface of your exchange box (or spam filter proxy).

This should be a very easy change for you.  Once you change the MX record, provided the exchange and firewalls are set up right, the mail should start flowing in to your box instead of the ISP's.

you must make sure that the user accounts have mailboxes on the exchange server, and that their email addresses correspond to the ones that already exist with your current host.
Mattia MinerviniAuthor Commented:
Thanks for ur comment...but let me understand better.
My exchange local account is: tom@domainxx.local
My isp mail is :
If i route e-mail to my exchange instead of isp mail server, how exchange manage this situation?

you say
"you must make sure that the user accounts have mailboxes on the exchange server, and that their email addresses correspond to the ones that already exist with your current host."
so ii's enough i modify my exchange local username from "tom" to "tom.smith"?

After this, exchange starts to route internal email only locally?
(it has to route only locally an e-mail from tom.smith@domainxx.local   to fred.smith@domainxx.local, but route outside an e-mail from tom.smith@domainxx.local to

What i'm no understanding if is exchange can coreectly manage domainxx.local and
You don't need to change your account names, just add a recipient policy that adds an email alias to all users:

more info  (

Otherwise internal delivery should not be a problem.
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Azeem PatelSystem AdministartorCommented:
a. You need to set accepted domain policy coz you have domail.local which exchange will undestand and you will have to add in accepted domain to Exchange will start accepting email id with
b. Create a reciepent policy so when new user is creaetd he has bolth email ID user@domain.local and and set as primary
Mattia MinerviniAuthor Commented:
Trying to closing circle...then i'll try in a test virtualized environment.
a) Migrate to an Isp for email and dns could provide me space and features (like Etrn...) better then actual isp (this step is forced by actual isp limits)
b) Pointing mx record to exchange public interface. At this time, exchange has to be set to accept, and all user of domainxx.local should have right "translation" for the user of by recipient policies
c) So exchange should be manage correctly inbox email (my goal is two mx record on my two adsl connection, third mx record on Isp Etrn service as backup). Having aliases with recipient policies, mail to goes to tom@domainxx.local.OK
And outgoing email? same benefit from recipient policies? Exchange let go out an e-mail from  tom@domainxx.local just like
d) publishing Owa, having Isp webmail like backup only for "outside" email and when my system is down
e) can i manage "delegates" in this situation?
Thanks again...

To migrate your email services to your exchange server you need to do following. This is a high level overview covering most of the aspects however  you may run into smaller config issues which can be take care after wards.

I will provide additional steps to the step you already have
a. ) make sure you have static public ip address. You outgoing emails will not work if you running dynamic public ip. They will  be termed as spam.

b.) you need to make sure that is authoritative domain

c.) backup mx needs to be highest preference so in case if other two mx are down only then it fails to backup mx

Outgoing email. You need to make sure that primary smtp address is set to instead of local domain

Yes you can manage delegates with in exchange env.


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
Mattia MinerviniAuthor Commented:
a) I have static Ip on primary dsl and static ip on secondary dsl. I want to set two mx record for these, my isp mail server like third mx for backup (etrn not available from my isp.....  =:-(     ).


c) which is the "best practices" approach, managing mx record? any info,articles, example please?

for exchange:
d1) setting an accepted domain policy (
for every internal adress:
d2) setting a recipient policy to get an alias ( & tom@.local )
d3) setting the primary smtp address on


c) which is the "best practices" approach, managing mx record? any info,articles, example please?
 It's easy to setup mx record. The only thing that you need to keep in mind is that the lowest preference mx record will be picked up first. Two mx record with same preference will respond in round robin fashion. The higher preference mx record if exist will only be picked up when lower preference record doesn't respond.
Mattia MinerviniAuthor Commented:
I have to try this teoric way...but people explained well and focus my needs.
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
Active Directory

From novice to tech pro — start learning today.