Is there a way to manually set what IP address/DNS record AD will use when replicating?
I have a "network within a network" (NWaN) setup which spans across two remote locations-- so there's one NWaN at Site A, then there's an IPsec tunnel connecting it to the second NWaN at Site B. The addressing's like this:
ServerDC1 (at Site A)
NIC1: 1.1.1.1/24 -- This is accessible from all internal networks, and can reach the internet.
NIC2: 1.2.1.1/24 -- This is a private, internal network, and can only be reached from the 1.2.1.x/24 subnet.
ServerDC2 (at Site B)
NIC1: 1.1.1.2/24 -- This is accessible from all internal networks, and can reach the internet.
NIC2: 1.2.1.2/24 -- This is a private, internal network, and can only be reached from the 1.2.1.x/24 subnet.
ServerDC1 and ServerDC2 are both DNS servers meant to replicate to each other, but they each contain DNS records for themselves and all the clients they deal with on both the 1.1.1.x/24 and 1.2.1.x/24 networks.
This creates a problem, as whenever I try to replicate between these two servers, they try to communicate using their nonroutable 1.2.1.x addresses rather than their 1.1.1.x address.
I can go through the DNS records on both servers and delete the references to the 1.2.1.x associated with these servers and then they'll replicate fine; but I'm not sure if any machines will need these records.
So is there a way I can tell AD to only use the 1.1.1.x address when replicating?
I've looked into split DNS, but I can't afford the downtime that it would require.