Internal and Public Using Same Domain Name

[Guest]

I have a customer who is using an Active Directory domain name of
CompanyA.com. Although they own the rights to the CompanyA.com domain name,
they have never used the CompanyA.com domain name on the Internet. Now,
they are thinking about spinning off a second company and allowing that
company to use the CompanyA.com domain name as their Internet presence domain
name.

What problems can this pose - having the first company use CompanyA.com as
their internal Active Directory domain name AND allow the second company to
use the CompanyA.com domain name as their Internet presence domain name
(e-mail, web server, etc)?

 

[Guest]

Well if the internal server stays internal and never goes external it would
be ok. But if you go external it would not know who's server to pull info
from...

 

[Joe Richards [MVP]]

This could cause various issues.

The first I see is that if people in CompanyA needed to access resources
(say like the web site of the new company with the CompanyA internet
name) they won't be able to because local DNS won't resolve it.

There could also be issues with mail delivery and possibly with later
attempts at Federation with any external company.


--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm