Our forest consists of the root "home.com" and two child domains 
"us.home.com" and "eu.home.com".  When I look at how the DNS zones are 
configured in DNS all three domains are separate meaning when I look in DNS 
manager I see

home.com

us.home.com

eu.home.com

The "us" and "eu" zone are *not* delegated from within "home.com". 

Working in the lab we did a new install to mimic our domain to test a few 
things.  However, after getting the test lab up and running the DNS zones are 
configured a bit differently.  We now have one DNS zone "home.com" and inside 
that domain we have two subdomains "us" and "eu".

Question:

How did our production active directory end up having "us" and "eu" as 
separate dns zones compared to a new AD install with Windows 2003 having 
those domains as subdomains within the forest domain?

Is that because the domain when it was first created was with Windows 2000 
and that's how AD would create the zones for child domains? 

Thanks

Amy

Amy M. wrote:
> How did our production active directory end up having "us" and "eu" 
> as separate dns zones compared to a new AD install with Windows 2003 
> having those domains as subdomains within the forest domain?

Where your "us" and "eu" zones originally served up by different (local 
to the physical location) servers?



Grant. . . .