Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm running Windows 2008 r2. I'm curious about creating a new domain in a new forest on a separate install as child.domain.local.

The issue is domain.local currently already exists in this network which I do not want to adversely affect. The new AD install will necessitate DNS, so I just want to ensure child doesn't interfere with domain.local.

share|improve this question

migrated from Aug 24 '12 at 16:51

This question came from our site for computer enthusiasts and power users.

That should not cause any problems from the Active Directory side of things, as the two domains will essentially be like ships in the night - they don't know or care about each other. What you will want to do is be careful about how you design your DNS infrastructure.

Consider whether you'll need to resolve names in the subdomain from a system that's using the "parent" domain's DCs for DNS, or the reverse - you might need creative delegation (NS records in the parent domain), forwarding (the subdomain's DCs using the parent DCs as their forwarder for recursive requests), or stub zones to account for the name resolution gap between your two Active Directory infrastructures.

Also consider that the search suffix of the systems in the subdomain by default would cause them to also search the parent domain's DNS for a hostname - this may cause some interesting and unintended problems.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.