Solved

Is there a conflict if our internal facing domain is different than out external facing domain.

Posted on 2008-10-08
4
472 Views
Last Modified: 2013-11-05
We are reconfiguring our domain names by switching our internal facing domain name. The reason for this change is our website uses our root domain name i.e. company1.com and best practice says they should be different. When we switch our internally facing domain name we would like to keep our email on exchange server the same i.e. mail.company1.com and change just the internally facing domain name to something different i.e. company2.com. Would there be a conflict with the domain controllers and exchange server if they had different names:

example
email: user@company1.com
website: www.company1.com
internally facing domain name: company2.com

It may sound confusing and any help is greatly appreciated. Thank You
0
Comment
Question by:bsmiley00
  • 2
4 Comments
 
LVL 2

Assisted Solution

by:emanteuf
emanteuf earned 60 total points
ID: 22671680
I usually use different internal and external domains.  The email domain and active directory domains don't have anything to do with each other.  You can also host multiple external email domains on a single exchange server and have an internal domain like company.local.  If you need any clarification, I'd be willing to go into more detail.
0
 
LVL 13

Accepted Solution

by:
markusdamenous earned 65 total points
ID: 22671696
No, this setup is absolutely fine.  My internal domain name is XXXXX.local and the public facing, I have a few, which end in .co.uk or .com.

Whatever the internal domain name is, ensure that works first.  Then, any additional domain names you just tell Exchange that it should receive mail for them.  You do this by address the domain name in a Recipient Policy.  this could be by adding to the Default Policy or by creating a new policy.  Once it is in here, it will propogate an email address using that domain name to each user.  You can choose the format, (first.last, initials, etc).

0
 

Author Comment

by:bsmiley00
ID: 22672829
Thanks for comment, it looks good. I do have other questions though. Currently our external facing domain "company1.com" is registered to us. We will keep that for email and web site etc.. etc.. However the internal facing domain we want to use is currently registered to another company.

Because its internal facing only, will there be a naming conflict?

Also will we be able to delete the internal facing domain from exchange server so we don't receive the other companies email or cause conflicts?
0
 
LVL 2

Expert Comment

by:emanteuf
ID: 22679210
If you choose to use the domain internally that's registered to another company it will not be a serious problem.  Since you will be hosting the DNS zone for that domain name, you would not be able to resolve names that are hosted by the actual authoritative DNS server for the domain.  This means your internal users would not be able to visit that company's web site.  You also would not be able to email that company unless you set up an SMTP connector for that domain that would send mail directly to their mail server listed in their MX record.  But I'm guessing that you don't do anything with that company, so you wouldn't really need to do anything.
0

Featured Post

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Public folders data to network share. 8 28
Exchange 2010 RU 16 5 42
problem with default throttling policy 2 22
Exchange 2016 DAG Witness Server 3 38
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

777 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