I have some very stringent access policies between subnets in the internal network, and as such there is not much in terms of information that needs to pass from one subnet to another. However, when I am resolving a name for different servers that need to be connected to different subnets, my systems start using the IP address of a different subnet to try and communicate with. For example: Client1 IP Address: 192.168.0.2 Server1 IP Address: 192.168.0.1, 192.168.1.1, 192.168.2.1 Client1 resolves Server1 to 192.168.2.1 Ping and other traffic fails Client1 to 192.168.0.1 Ping and other traffic works correctly As such, I am needing to figure out a way to get the DNS server or the DNS client to use the addresses that are retrieved for a name for the current subnet instead of another subnet. Any tips or tricks anyone can give me on how to make this happen?

I am reading your question , but it confuses me a lot. Please answer this How Server1 has 3 different IP address? Idellay, only one IP address has to be assigned to any of the network device. I am not sure about server1 IP address. Please explains bit more on this and your scenarion also. Regards, _Prashant_MCSA|MCITP SA|Microsoft Exchange 2003 Blog - http://prashant1987.wordpress.com Disclaimer: This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Hi, If you server have these multiple IP addresses both registered in DNS server, it is expect that it can resolves to other subnet IP address. It cause by DNS round robin. For detailed information about round robin, please refer to following article. Configuring round robin http://technet.microsoft.com/en-us/library/cc787484(WS.10).aspx You can also restrict other IP addresses register in DNS, so can only resolved to one IP address. Just curious, why you need to have your server hosts multiple IP addresses in the different subnets? Best Regards, Aiden Aiden Cao TechNet Community Support

The server in the example is hosting VMs that have access to 3 different subnets within the system, and thus to allow cluster communications to operate correctly for these networks, each node in the cluster has IP addresses on each subnet.

I am having the servers have NICs and IP addresses in those networks so that the information that is tansmitted between the systems that are on those subnets to these specific servers stays on that subnet and does not have to go through a router or other device as I am isolating the different subnets from each other in almost entirity.

Like Aiden_Cao told, me too Iam curius why you need multiple IP per server. Usually in a enviroement with multiple VLAN I am more used to see a VLAN only for your server, thus the access rules would be in the switch to what is allowed or not.MCP | MCTS 70-236: Exchange Server 2007, Configuring