We have 2 different locations, and at both site we have multiple domain controllers (Win2008).
In our application we use Serverless Binding to execute our LDAP queries http://msdn.microsoft.com/en-us/library/ms677945(v=vs.85).aspx.
If we look at de DnsHostName of the LDAP://RootDse on site B we always get the default domain controller of site A. Therefor all LDAP queries go much slower.
Is there a way to change the default domain controller per site ?
Best Answer
This can occur if someone has adjusted the domain controller's DNS priority (or weight) so that lookups would prefer a dc over another. (LdapSrvPriority)
The _ldap values are observable in the dc._msdcs.domain.com dns zone.
This may also occur if someone has adjusted the Netlogon service so that the DNS mnemonics for the LDAP SRV record is not registered, or if one site is configured to register records for another site (Site Coverage).
How to optimize the location of a domain controller or global catalog that resides outside of a client's site
http://support.microsoft.com/kb/306602
DNSRegistrationSettings
http://msdn.microsoft.com/en-us/library/gg251208%28v=prot.10%29.aspx
How DNS Support for Active Directory Works
http://technet.microsoft.com/en-us/library/cc759550%28v=ws.10%29.aspx