Child Domain with Windows 2000 Active Directory

  • Thread starter Thread starter Dylan Kulesza
  • Start date Start date
D

Dylan Kulesza

I have a domain ecm.com in which I have an Exchange Server, 2 Domain
Controllers and member servers and clients. We have another branch
that we want to link AD with. From Reading/Experimentation creating a
child domain via dcpromo renders a new domain with seperate
username/password and computer accounts. However, this is not the
implementation I want/require so I have decided to use AD with Sites
for my domain. However, I would like to setup DNS namespace for
autx.ecm.com and satx.ecm.com and have my exchange and member servers
on ecm.com. (Which I am currently *tinkering* with and am having
trouble delegating the subdomain and what not) Am I looking in the
right direction, or should I just setup a seperate domain for SATX and
a seperate domain for AUTX and then my parent domain ecm.com and setup
trusts or is this *overkill*? We only have 30 computers +/- 5 in each
Site.
 
I don't have any Exchange knowledge (and not much AD knowledge either,
but...)

With the number of clients and users you're talking about, a single
Domain should be more than sufficient. You can make your AD Domain
ecm.com. When you do that, you'll need DNS working with ecm.com. You
can additional create the autx.ecm.com and satx.ecm.com DNS domains on
the same DNS servers. This assumes you will only have internal clients
hitting these DNS servers. If it's going to also be public (Internet)
clients, this isn't a good idea as you don't want them to be able to see
your AD records.

So, you should end up with an AD Domain called ecm.com (which is also a
DNS domain), and then 2 DNS domains for your other domains. Hope that
makes sense.
 
Dylan,

The main purpose of a "site" is to let you control traffic.

If you want to have multiple DNS names, then you may want to set up multiple
AD domains but that may add more problems than you want.

What is your reason for wanting multiple DNS names? If it is just for email
purposes, you can get there a lot easier by using an Exchange 2000 policy.

For example, most of my staff have Alionscience.com as their main address
BUT I also have about 30 who need HFACTORS.COM as their main address and 3
or 4 others who need DOD21CT.ORG as their main address.

I have all of these in the same domain, and on the same exchange server(s).

For a small number of users, this would be easier to run, than multiple
AD's.

Ed
 
Back
Top