Add a domain controller from another network?

[David Sworder]

Hi,

We have two offices in two different states. Office A is on network
192.168.1.0/24 and Office B is on network 192.168.2.0/24. The two offices
can exchange IP packets via the bidirectional demand-dial interfaces in
Routing and Remote Access. Ping tests work fine between the networks.

I want the computers in Office B to be in the same domain as those in
Office A. My first task is to add a domain controller to Office B. Adding
secondary domain controllers has always been straightforward enough when all
DCs are on the same network. However, are there any snags that I might hit
when trying to make a computer in Office B a secondary domain controller of
a domain that until now only existed in Office A? How do I tell this
computer in Office B that the "master" domain controller is on the
192.168.1.0/24 network? Will the DNS on the Office B domain controller
automatically synchronize with the DNS records held on the DCs in Office A?
I'm just not sure how the computers are supposed to "find" each other to
start the synchronization process.


Thanks,

David

 

[Bjoern Wolfgardt]

Hi,

you should install a DNS Server on both Networks. Clients on Network A
should get the DNS on Network A as the primary DNS. Same applies to Network
B. Create the Sites in AD Sites and Services and move the DC to the sites
which they belong to.
Each DC will find the replication partner by DNS query. You should also
configure the replication connection in AD Sites and Services to only
replicate at selected times. If you don't do so you will get a high
telephone bill because the DCs will replicate when ever they want. Sometimes
there will be a connection when it is not time to synchronize. This will
maybe be time sync or something else.

hope this helps
Bjoern Wolfgardt

 

[David Sworder]

thanks!

Hi,

you should install a DNS Server on both Networks. Clients on Network A
should get the DNS on Network A as the primary DNS. Same applies to Network
B. Create the Sites in AD Sites and Services and move the DC to the sites
which they belong to.
Each DC will find the replication partner by DNS query. You should also
configure the replication connection in AD Sites and Services to only
replicate at selected times. If you don't do so you will get a high
telephone bill because the DCs will replicate when ever they want. Sometimes
there will be a connection when it is not time to synchronize. This will
maybe be time sync or something else.

hope this helps
Bjoern Wolfgardt