Solved

Internal Business Exchange Server

Posted on 2012-03-24
3
622 Views
Last Modified: 2012-04-09
My business is moving to an internal Windows Server 2003 Enterprise Edition server running Exchange Server 2007 from GoDaddy's mail.

The server is set up and I need to know what is required to make the move so that when the changes finally propagate through, mail will be able to be sent and received without problems.  I also want to have the webmail working through OWA.  The existing domain will still be hosted with godaddy.

Example:
mydomain.com - web hosting at godaddy

my internal server ip - 192.168.123.123
my external ip (which is a static ip): 123.123.123.123

mail.mydomain.com
email.mydomain.com
mydomain.com/owa

What should I change in the GoDaddy DNS records, MX, A and CNAME....  I noticed GoDaddy has many different domains pointing as mail.....

for example,  e.secureserver.net, email.secureserver.net, webmail.secureserver.net

And what about the smtp.secureserver.net and pop.secureserver.net and imap.secureserver.net

I also saw mobilemail in there....    and a pds cname??

What should my MX records look like as well.

Hope someone can help me.
0
Comment
Question by:the-miz
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 14

Expert Comment

by:Kaffiend
ID: 37762307
mydomain.com/owa will not work for you.  Sorry.  (Unless you want your domain's webserver to also be hosting Exchange)  It should be mail.mydomain.com/owa or something like that.  Anyway, you don't have to specify slash-owa anywhere, as far as DNS is concerned.

You need to basically change your MX record - this tells other mail servers the IP address of your domain's mail server.  When another mail server needs to send email to someone in your email domain, it will query DNS for your domain's MX record.  Then, that mail server will try to send email to the server with the IP address of your MX record.  Make sure there is only one MX record, and that it points to your Exchange server.

All those other ones - whatever.secureserver.net - get rid of those records when you're ready to make the switch.  They're not necessary anymore if you're running your own mail server.  

I also suggest you change the TTL of your MX record to a short interval about a week or two before you do the switch.  If a record has a short TTL, servers will poll more often for that address, and as a result, any changes to your MX record will propagate faster.

Don't forget to make sure your ISP (not GoDaddy) creates a PTR (Reverse DNS) record for your mail server.  Without this record in place, you will find that some mail servers will not accept mail from your email server.  Example, if your MX record points to mail.mydomain.com, have your ISP create a PTR record with the value mail.mydomain.com
0
 

Author Comment

by:the-miz
ID: 37762650
mail.mydomain.com is just fine and I prefer it,  but in the next week or two after this change, we are moving our web server to an internal one as well.

So basically:

Step 1 - Change TTL interval a week before switch to a short one.

Step 2 - Remove all the *.secureserver.net, change the MX record to point to me 123.123.123.123 (for example)

Step 3 - Have my ISP add a PTR record for my mail domain to point to my 123.123.123.123

Then wait for everything to propagate through cyberspace.
0
 
LVL 14

Accepted Solution

by:
Kaffiend earned 500 total points
ID: 37763429
As far as DNS goes, that's probably it.

Another record that is useful (for Exchange) is autodiscover.  Set this to the same IP address of your mail server.  This record will help with phones, and email access using Outlook while offsite.
0

Featured Post

Enroll in June's Course of the Month

June's Course of the Month is now available! Every 10 seconds, a consumer gets hit with ransomware. Refresh your knowledge of ransomware best practices by enrolling in this month's complimentary course for Premium Members, Team Accounts, and Qualified Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to install and use the NTBackup utility that comes with Windows Server.
This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question