Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 609
  • Last Modified:

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

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.
0
bbcac
Asked:
bbcac
  • 2
1 Solution
 
CollinsTSCommented:
Are your Active Directory Sites & Services sites configured correctly?
0
 
bbcacAuthor Commented:
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
0
 
CollinsTSCommented:
http://technet.microsoft.com/en-us/library/cc978016.aspx

I'd read the above. Unless this is causing a problem, it's not really an issue. DNS lookups for logging in to a domain work differently than those used for ping.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now