Ok so Sites are separated by WAN
Domain : production.contoso.local SITE A Site network: 192.168.0.0/16 Site DCs : DC1-SiteA, DC2-SiteA Client : serverA SITE B Site network: 172.16.0.0/16 Site DCS : DC1-SiteB, DC2-SiteB Client : serverB
Randomly servers seem to resolve the domain name to DC in another site.
I will logon to a serverA(192.*) and ping our domain "production" and it will resolve to the ip of a DC in a different site(DC1-SiteB, 172.16.0.0/16), while on the other hand if I ping the domain using the full fqdn "production.contoso.com" then I will resolve to the correct DC(DC1-SiteA, 192.168.0.0/16)
If I flushdns, then the situation reverses it's self, "production" resolves to DC1-SiteA(192*) and "production.contoso.com" resolves to DC1-SiteB(172.*).
All Clients and Servers are reporting as being in the correct site via http://www.powershellmagazine.com/2013/04/23/pstip-get-the-ad-site-name-of-a-computer/
DCDiags checkout on all DCs
All DNS records and _msdcs look correct.
If the domain resolves to a DC in another site, is it pullling policies and authenticating to those, thus slowing logon/reboot times?
Any other avenue I need to check?