How to competently replicate a domain controller to another building via WAN?

Question

Domain Name System

Making a CD replica within the same network is not difficult. But when the second CD is located in another building and is connected to the first via VPN, there are some difficulties.
I would like to do the following:
- make a VPN tunnel to the first building in the second building (done)
- set the roles of AD, DNS, while selecting replication from the CD located in the first building. (resolved)
- replicate user profiles using DFS tools so that the second building has an up-to-date version of the employee's profile.
Let me explain: in the user properties, the network storage will be specified using the FQDM name (for example: \\dfs.office.org\profiles\username).
It's not clear here. It is not difficult to make DFS and a replica, but how to make client cars choose for themselves the nearest resources for authorization (CD in the right building) and choose the nearest server with profiles so as not to pull their profile from another building when entering.
In general, tell me where to dig? Make CNAME in replicated DNS to nearest server with profiles?
If authorization on a CD in another building can be forgiven, there is little traffic (although there is still a GPO), then loading profiles through the Internet is a fatality.
Thanks for the help!

Answer 1

For such a division of the network, it is necessary to break the domain into sites (places). They are determined by the subnet address and all operations in AD are carried out first with the controller in the same site, then, if it is not available, then with the remote one. The path to the roaming profile can be set as %logonserver%\path\%username%
A couple of small annoyances - WinXP and WinVista+ have different versions of profiles, if the user works with both systems, then there will be two different profiles. If the user forgot a 10 gig file on the desktop, then it will honestly be synchronized when entering / exiting.