How to configure DC maintenance priorities for sites in AD?

Question

Active Directory

Colleagues, there was such an unusual question:
There are several sites in AD, each of which is headed by 2 DCs. Bridgeheads, replication schemes are set up, but such a funny incident arose:
At the start, the machine from Site1 crawls for policies not on the controllers of its site, but anywhere, pulling policies from others. Sometimes this leads to unusual results when, for example, the machine receives a list of printers from another office and starts briskly printing on them.
Any ideas how to set service priorities so that site machines climb to site controllers, and if maintenance is not possible, they already climb where they please?

Answer 1

The process of discovering the owner of the GC occurs by subtracting SRV records from the directory:
_tcp.NameOfYourSite._sites._DC._msdcs.YourDomain
The computer sends ldap-ping to these controllers, waits for a response, if there is no answer, it goes back to the DNS, with a search for other controllers, in other sites. This is where the cost of site-links between sites comes into play. Well, inside the site, the priority is determined through the weight and priority of the srv-record.
Here by such rules, instead of "where it will please them" there are machines in the domain. This is the most accurate description.)