I have a Domain connected Windows 2008R2 server acting as secondary DC with two active NICS. One NIC is the LAN with Static set (192.168.x.x) and has internet access and is connected to a switch which feeds the rest of the LAN. The other NIC is isolated and connected statically (10.65.x.x) to a separate switch which iSCSI backup traffic runs over. The 10.65.x.x network is separate from the LAN. This iSCSI NIC has an IP and subnet but no other settings. "register this connection in DNS" is unchecked. DHCP and DNS run on this server as well, replicating with the Primary DC at the corporate office.
The issue is, within DNS, the 10.65.x.x address keeps adding itself along with the 192.168.x.x address, both pointing to (Server1) From another location, if I ping back to (Server1), it returns the 10.65.x.x instead of the 192.168.x.x address. Not sure why it trumps the 192.168.x.x address. Anyone outside of our LAN trying to get to my SharePoint server at that point, get a "page could not be displayed" until I go into DNS and remove the 10.65.x.x entry which allows the 192.168.x.x to resolve properly to (Server1)
On (Server1) Under Control Panel\Network and Internet\Network and Sharing Center\Active Networks, Both NICS are listed as Domain Network connections. On my other servers (Server2) and (Server3) that also use the same two NIC Setup for iSCSI backup traffic, they are in separate locations (screenshots showing difference below)
I need to keep the 10.65.x.x address from showing up in DNS so (Server1) resolves to the 192.168.x.x address only. I have to delete the 10.65.x.x address from DNS every few days, can't really put a finger on when it adds itself back, sometimes it may stay deleted for a week. Could the reason for all this be the two NICS belonging to the same location? If not, what can be done to keep the 10.65.x.x address out of DNS?