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!