Yeah, always the same one. And it's the same one that returns first when you do a nslookup on my domain. Probably not a coincidence.
DNS has _ldap and _kerberos records to work this out, but nothing for straight up TCP. I'll just tell my developers to bind a different way so that it uses...
No, the DC is on a different subnet than the clients. Yes, I setup all the subnets in this building to the same site. I guess my question is "What determines which DNS record is returned when a client requests it?"
Again, keep in mind, these aren't ANAME records. We have 22 regional offices...
That is the way I understand it also, except it's not working that way. Instead of the DC responding that resides in this site, a regional or remote server is responding over a 56K line. I originally thought DNS would work it out automagically, but it isn't. FYI: The two DNS servers that are...
When I ping my domain name corp.vha.company a remote domain controller responds. When I $> nslookup, it shows all of my DNS / Domain Controllers, and the first one is the one that responds, but it isn't local.
The problem is that our developers all point to server names and we want them to...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.