• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 181
  • Last Modified:

Exchnage Server as secondary server with the same domain name

Hi,
 I am new to the exchange world and i am trying to set up an exchange server as my email server for a domain i already have on a linux server. i want to keep my web page on the linux server and have my emails for that domain hosted on another server with windows server 2003 and exchange server 2003.

how would i go about changing the MX records to reflect the settings for the new email server and vise verse? or how would i go about setting up the ms server to look for emails. setting up name servers, mx records, etc. to just look out for email and not domain requests.

i also want to make sure that OWA is set up on the exchange server and do not want the clients to have to type in an ip address to get to the web based email client. i want them to type in www.doamin.com/exchange not 123.123.123.123/exchange

the new server has not been issued yet. i am just trying to get as much information as i can before i set it up. i have had a small amount of experience setting up exchange server in the past and this is a little more advanced for me.

I have set up an exchange server on a test enviroment in house but haven't had much experience outside of that.

0
slowlyfading
Asked:
slowlyfading
  • 4
  • 4
  • 3
2 Solutions
 
bluetabCommented:
You need to edit your DNS entries on your Public DNS server.  Presumably this is your domain name registrar as well.

Setup the following:
MX Record:  mail.domainname.com  Priority 10
A Record: points mail.domainname.com to your Public IP address of your Exchange Server

I'm assuming that your Linux and Exchange server are on the same network.  In order to use OWA you will need to make sure that both servers have their own Public IP address and configure your router/firewall accordingly.  Once you setup the DNS records and they propogate the Internet (usually 24-48 hours) your users will be able to access OWA by typing https://domainname.com/exchange.  
0
 
slowlyfadingAuthor Commented:
even a good tutorial would help if it is too much to explain. i have searched all over the web with no luck. i am currently reading the exchange deployment and administration guides but they are a sea of nothiness related to what i am trying to do.
0
 
Hypercat (Deb)Commented:
bluetab has given you just about all you need to know to set this up except how to install Exchange.  Proper DNS configuration is very important for Exchange to work properly.  One of the things he/she didn't ask or mention is whether you are already running an internal DNS server on this network.  If so, you will need to set up your new Windows 2003 server to use that DNS server, or else move DNS from the existing internal DNS server to the Windows 2003 server.  That's for internal name resolution only, though. As far as getting email and OWA to work, it's all based on the external DNS configuration.  

The Exchange 2003 deployment wizard pretty much walks you through everything you need to do to set up Exchange initially.  As long as you are knowledgeable about general networking and Windows 2003 domains specifically, you should be OK with that. Just be sure you follow the steps carefully and read everything pertinent to each step before you do that step. OWA is set up automatically on the Exchange server when you install Exchange. All you need to do is be sure that you have installed IIS and SMTP as part of your Windows 2003 server installation.
0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
bluetabCommented:
If you are looking for installation and configuration tips on installing Exchange this is a great site:
http://www.petri.co.il/exchange.htm

My recommendations would be to follow the steps outlined on the Exchange CD for the installation.  After that you can use the information in the site above to configure OWA,
0
 
bluetabCommented:
Good points hypercat.  I didn't see your post before I responded.
0
 
slowlyfadingAuthor Commented:
The linux box that i am running is currently the DNS server for mydomain.com. The windows server has not been installed yet but will be installed on the same network. Will i still be able to use the linux box as my dns and have the windows box just function as my mail server for mydomain.com.

in setting up windows server 2003 do i name the server mail.cotapaxi.com as the domain?
0
 
bluetabCommented:
If you have a domain in your environment where the Windows server is the DC the Windows server should also be the DNS and DHCP server.  If it is not you will experience a lot of other issues down the line.  

I would recommend setting up the internal domain as: cotapaxi.local.  Then name the server whatever you want; server, exchange, fileserver...
0
 
Hypercat (Deb)Commented:
Not being a Linux person, I'm not sure about running DNS on Linux with a Win2K3 domain.  You should probably post a question in the Linux section on this.  A Win2K3 DC on its own domain needs to be it's own DNS server.  You might be able to share the DNS zone between the two but again, I'm not any kind of expert on this. Do you have/will you have any workstations connected to this network?

You would want to name your internal Win2K3 domain something different from your public domain name, such as local.cotapaxi.com or, as suggested by bluetab, cotapaxi.local (although I have somewhat of a prejudice against the ".local" naming convention, it is recommended by Microsoft).  You would configure your email domain, however, to match your public domain name so that your email addresses are correctly configured as "username@cotapaxi.com."
0
 
slowlyfadingAuthor Commented:
Nope there will not be any workstations connected to the windows server. Only Outlook would be connected to this server. i have found ways around what i am trying to do but the thing is changing our email domain would be such a hassle.

i have servers set up in house that are local machines. i guess when you strip the question down to the core it turns out to be a cross integration between linux and windows using the same domain name for different purposes.

now i understand the windows environment and it's interaction between dc, dns, and ac. but what i need is to set up a dedicated windows server in a data center next to my dedicated linux server using the same domain name. linux server controls the website and the windows server controls all email handling.

0
 
Hypercat (Deb)Commented:
You would not have to change your email domain at all.  You can configure Exchange to use whatever email domain name you are currently using - it does not have to correspond to the Windows domain name that you use when setting up the Windows server.  Exchange using something called a Recipient Policy which you configure through the Exchange System Manager GUI to control the email domain name.  It will default to using the same domain name as your Win2K3 domain name, but you can easily change this to match your existing email domain name.
0
 
slowlyfadingAuthor Commented:
Thank you!
0

Featured Post

Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

  • 4
  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now