Disable automatic DNS registration in a DNS server

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.

Who is Participating?
Computer101Connect With a Mentor Commented:
PAQed with points refunded (500)

EE Admin
Is WINS enabled on this box?
If so, try to disable WINS. Maybe there's a connection between your DNS and WINS database.
If, WINS exists.
Mark PavlakCommented:
Have you unchecked regsiter DNS then delete the A record and the asicatoed pointer?
Easily Design & Build Your Next Website

Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.

Linette_LaimingerAuthor Commented:
Oh yes - multiple times.  I can now officially do it in my sleep.

We found the solution.  Go to the KB 246804 article and look under the area "DNS Server Service" - it's about halfway down the article.  You have to create the REG_SZ subkey PublishAddresses (in the proper place), and then stop/start the DNS service to apply.  I've been watching the DNS now for 30 minutes and it hasn't regenerated the 172.29.183.x addresses (for either server), so apparently MicroSoft was aware of the problem.

Problem solved.  Thanks!  Add it to your Knowledgebase.
ive seen this before and this doesnt always work but you could give it a try. In the DNS console, open the properties of the affected server and under the advanced tab, untick enable round robin. It has worked for me in the past when i have had NIC's autoregistering themselves when they shouldnt be. Hope this helps
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I will leave the following recommendation for this question in the Cleanup Zone:
PAQ - Refund

Any objections should be posted here in the next 4 days. After that time, the question will be closed.

KCTS: Experts Exchange Cleanup Volunteer
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.