I have three racks of servers (the majority of them are Win2003 SE) that I configured over the weekend to have a second NIC dedicated to performing backups, and ONLY backups. Two NIC's are in each server, the "primary" one has an address of 192.168.1.x and the NIC used for backing up is at 172.29.183.x (I match the last octeton each NIC to avoid confusion).
The 172.29.183.x NICs are physically wired into a separate switch that is NOT routed internally, users can NOT see this network and CDP (Cisco Discovery Protocol) cannot find it. So far, so good, this is what I need to happen.
On the backup link interface setup, in the Advanced tab, in the DNS tab there is a check box that says, "Register this connection's addresses in DNS". I DON'T want this interface's IP registered in DNS, becasue it then hoses up DNS entries for authentication to the 192.168.1.x subnet. This DNS non-registration works properly on each and every server BUT (and here it comes!) the two DNS servers I have! Yep, that's right, the DNS servers rudely register their "backup" NIC IP's in the DNS registry irregardless of whether that do-not-register box is checked. Those are the most important IP's that I *don't* want registered, yet I can't get rid of 'em.
Here's what I tried, to no avail:
1) Un-check the "Register this connection's addresses in DNS" box for BOTH NIC's
2) Applied the DWORD DisableDynamicUpdate per the KB article: http://support.microsoft.com/kb/246804
- note that this affects BOTH NIC's per the article.
Here's the interim solution, which of course is NOT acceptable:
1) Disable the interface (NOT unplug, just disable).
To recap: DNS non-replication of a specific NIC works fine on a non-DNS server. On a DNS server, it won't shut up unless the interface is disabled.