Domain controller is registering additional network interface IP into DNS
We have a Windows 2003 R2 Domain controller which has two network cards. One network card goes to the LAN (10.30.0.0/16), and the other goes to a SAN (192.168.10.0/24). For some reason, the IP address for the second network adapter is registering in DNS.
On the server, I have opened DNS management console and configured the server to only listen on the LAN interface. I have also configured the SAN network connection to not register the connection's address in DNS.
What else am I missing? The IP address for the SAN interface keeps appearing in DNS as an A record for the domain. I manually delete it but it re-appears after a day or so. When it shows up in DNS, client computers sometimes will not run logon scripts etc. Any ideas?
On the server, I have opened DNS management console and configured the server to only listen on the LAN interface. I have also configured the SAN network connection to not register the connection's address in DNS.
What else am I missing? The IP address for the SAN interface keeps appearing in DNS as an A record for the domain. I manually delete it but it re-appears after a day or so. When it shows up in DNS, client computers sometimes will not run logon scripts etc. Any ideas?
ASKER
As I said in my description: "I have also configured the SAN network connection to not register the connection's address in DNS."
Also, sometimes it is necessary to have a second connection on a DC. This should not be a problem.
Also, sometimes it is necessary to have a second connection on a DC. This should not be a problem.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sorry missed that. Do you have DNS servers in the TCP\IP properties on the second NIC?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As a note, this problem has existed since Windows 2000 and still exists in Windows 2008 (Dealing with it on my test network, since I have a second NIC dedicated to a Hyper-V for SBS 2008 testing. I just configured the second NIC not to register in DNS, so I'll find out if the lack of respect for that setting still happens in Win 2008).
2008 is a different beast, would be interested in your thought about w08. As for the question above, I guess we need to have more information or more precisely more diag information (logs, etc) to give a good answer to the problem or find the problem.
Windows 2008 does it to, apparently.
ASKER
Thanks for the replies, everybody. I just spoke to the rest of my team and we decided to use this problem as an excuse to build a new (2008 R2) domain controller which is single-homed and then demote this dual-homed machine.
We do in fact have another domain controller in another site which is dual homed and is NOT demonstrating this behavior but it is noted that it could happen in the future so we will be prepared.
We do in fact have another domain controller in another site which is dual homed and is NOT demonstrating this behavior but it is noted that it could happen in the future so we will be prepared.
Probably your best bet. Dual NIC DCs are a pain.
DCs should not have multiple NICs one them. I would recomend to disable the second one.