<div>
Are your Active Directory Sites &amp;&nbsp;Services sites configured correctly?
</div>


Are your Active Directory Sites & Services sites configured correctly?

<div>
I think so... I have added the subnet associated it to site, added the site links to the proper hub domain controllers, and added site link bridging to the other domain controller by adding both the original site link and the hub to hub site link
</div>


I think so... I have added the subnet associated it to site, added the site links to the proper hub domain controllers, and added site link bridging to the other domain controller by adding both the original site link and the hub to hub site link

<div>
<div class="content wysiwyg-content">
We have an Active directory with hub and spoke topology. We have two datacenters and several remote sites. Half of all remote sites are setup with site links to one of the datacenters. There is also a site link between the two datacenters. I then setup site link bridging incase one of the datacenters is lost. <br />
<br />
This seems to be working, however on some of the clients in one remote site, when you ping the domain name (domain.com) it occasionally resolves to a domain controller at a remote site. We do not allow communication between these sites so the ping does not work. Why is this happening? I don't know if there are actually an issues because of this, but it seems weird that this would even happen.
</div>
</div>


We have an Active directory with hub and spoke topology. We have two datacenters and several remote sites. Half of all remote sites are setup with site links to one of the datacenters. There is also a site link between the two datacenters. I then setup site link bridging incase one of the datacenters is lost. 

This seems to be working, however on some of the clients in one remote site, when you ping the domain name (domain.com) it occasionally resolves to a domain controller at a remote site. We do not allow communication between these sites so the ping does not work. Why is this happening? I don't know if there are actually an issues because of this, but it seems weird that this would even happen.

Pinging domain name resolves to Domain controllers that are not accessible by clients

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.