AD integrated DNS replicates "same as" accross WAN

[Guest]

The setup: I have a single domain (i.e. mydomain.com) that spans two sites
with DCs at each site. The sites are connected via a VPN connection between
two routers. The sites, subnets and site links are correctly configured.

The problem: The local IP addresses for each DC are registering in the
domain's DNS zone as <ip address> A "(same as parent folder)".

The question: Will this create a condition where the incorrect IP address is
returned for a site, i.e. At site1, mydomain.com resolves to the IP address
of site2? Could this cause authentication performance issues?

Thank you,
Rick S.

 

[Jonathan de Boyne Pollard]

The problem: The local IP addresses for each DC are registering in the domain's DNS zone as &lt;ip address&gt; A "(same as parent folder)".
As they do.
The question: Will this create a condition where the incorrect IP address is returned for a site, i.e. At site1, mydomain.com resolves to the IP address of site2? If it is "incorrect" for computers in one part of the (Microsoft) domain to talk to computers in the other part of the domain, then it was probably incorrect for the domain to span two sites in the first place.