We have a handful of computers (about 10 out of 350) that will receive the IP address of a domain controller in a different site when trying to resolve the domain. From these computers we will ping domain.com and then run ipconfig /flushdns and then ping domain.com again. As we repeat this process over and over we will receive a different IP and cycle through all DCs in the domain.
We have 6 domain controllers in our domain and AD Sites & Services is configured as follows:
Site1
DC1 (192.168.128.11)
DC2 (192.168.128.12)
DC3 (192.168.128.13)
Subnet = 192.168.128.0/24
Subnet = 192.168.132.0/24
Site2
DC4 (192.168.150.11)
DC5 (192.168.150.12
Subnet = 192.168.150.0/24
Site3
DC6 (192.168.151.11)
Subnet = 192.168.151.0/24
One of the computers that is having this problem has the IP address 192.168.132.75, however the majority of the other computers on the 192.168.132.0/24 subnet do not experience this same problem. What can we do to figure out why this computer does not resolve a domain controller in the correct site?