asked on Adding Parent AD DNS Zone to an existing child DNS Zone
Our current AD domain name is similar to x.y.com. We currently have an external DNS for y.com (non-AD "Parent"). It appears that we can add the y.com as an AD integrated zone to our DCs, even though it is essentially the "parent" of our existing zone. It is like brining in a new parent to an existing child domain, if that makes sense. It resolves any added DNS entries under the parent y.com Zone in AD DNS, but will it cause any issues with AD?
Doing some testing, any DNS resolution will use the x.y.com domain first, then the y.com domain, which is what we want.
I was not sure if you can add a new parent to an existing child, as I was always told the "child" will think it is the top level for that domain (since it is the only one). But maybe that is only for AD Domains and not DNS Domains as they are semi-seperate in this case.
So are their any concerns with doing this in a production environment? Any downsides or things we need to test? If at worst case, we need to remove the new Zone from AD DNS (Integrated), will that cause any foreseen issues? Are their any white papers or information from MS? Thanks!
Doing some testing, any DNS resolution will use the x.y.com domain first, then the y.com domain, which is what we want.
I was not sure if you can add a new parent to an existing child, as I was always told the "child" will think it is the top level for that domain (since it is the only one). But maybe that is only for AD Domains and not DNS Domains as they are semi-seperate in this case.
So are their any concerns with doing this in a production environment? Any downsides or things we need to test? If at worst case, we need to remove the new Zone from AD DNS (Integrated), will that cause any foreseen issues? Are their any white papers or information from MS? Thanks!
Windows Server 2008DNSActive Directory
Last Comment
Mahesh
You will not able to add parent domain to the Windows AD infrastructure.
ASKER
Actually I was already able to add a parent DNS domain (y.com) as an AD Integrated Zone in our test environment (x.y.com). My question relates to that and what affects it may have, but it does appear to be working.
I did not add an AD Domain, only a DNS Domain.
I did not add an AD Domain, only a DNS Domain.
You need to add conditional forwarding in child domain pointing to parent domain and its dns server ip address.
U don't required ad integrated zone of parent domain in child dns server.
Alternatively you can enable zone transfer on dns zone in parent domain for child dns server
and add secondary zone in child dns server pointing to parent dns server as master
Thanks
U don't required ad integrated zone of parent domain in child dns server.
Alternatively you can enable zone transfer on dns zone in parent domain for child dns server
and add secondary zone in child dns server pointing to parent dns server as master
Thanks
What do you intend to accomplish by doing this? I'm fairly certain it can be done, but I don't see the purpose behind it.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.