I am a noob with Active Directory, and I know just enough to have gotten our current setup running fine.
We run a web farm with several web servers connecting to a file server for content storage. We are in the process of adding in a second file server and getting the two synched up with DFS-R. That all works great. I've also set up a DFS namespace so all the web servers can talk to the namespace, to make an automatic failover situation possible. That works great, too.
EXCEPT, here's the issue. Our hosting provider has two NICs on each server it provisions. A public adapter, and a private adapter. Before I went down this road of using DFS namespaces, I've always used internal 10.x.x.x IPs to access various servers (old habit, I know I could be using the computer name). Therefore, all traffic before now happily flowed across private adapters.
Now that I'm trying to use DFS namespaces, and therefore non-IP-based naming, I noticed that content being pulled in from our file servers is coming in over the public adapter instead of the private adapter.
The question: How can I force Active Directory DNS to resolve to the private 10.x.x.x IPs instead of the public IPs? Yes, those 10.x.x.x IPs exist in the DNS already.
The base domain and each computer in Active Directory have multiple A (and AAAA records) apiece. Is there a way to have DNS respond with a "preferred" IP?