stop server from registring two nics in DNS

how can I stop a multihomed server from registering both nics in DNS? It is causing authentication issues, we've removed the entry but it keeps re registering itself. Anybody know where I can go or do to stop it from registering this second nic, it is plugged in to a different subnet and doesn't need to be registered as an interface for the DNS server.

Find more posts tagged with

SAVE $250 on Your Boot Camp — Use Code "EXAM26"

Exclusively for TechExams members for Infosec Boot Camps starting before April 30, 2026

View Boot Camps

Comments

royal

http://support.clover.net/DNS_Update/dns_update.htm

Make sure the bottom 2 check marks are removed in the TCP/IP properties of the connection you do not want registering in DNS.

jkstech

that's the fun part, it's already unchecked.....

Ahriakin

If it's a DC you're in hell....There is a way to stop it but it's fairly complicated (way beyond the normal methods for disabling registration). I ran into this a few months back and while I did eventually google my way to a solution it wasn't worth doing so I just removed the extra NIC.

dtlokee

jkstech wrote:

that's the fun part, it's already unchecked.....

If it's an old regristration that's still in DNS you may just need to delete it, then it won't re-register it in the future.

illmatic3285

Yeah if it's a DC there is a lot involved because that will most likely caue master browser issues

CoryS

As long as you maintain the IP designated to your clients for primary DNS you are fine if this is a DC that no longer requires the 2nd interface (assuming maybe you used this for dhcp or something like that?), in regards to the master browser, even if elections happen and a client takes over this service it will be a non-issue since when you bring online your dc it will say that it is the master browswer and in all likely hood an election will take place and your DC should take back the role, otherwise give it time and it should take it back sooner or later

. I am not sure the time interval for this process but it is not critical like losing your PDC emulator or something

this is one of those things i wish would have been a yellow warning in the logs and not a red x

So.. follow royals recommendation and delete the records, uncheck those radio boxes, and you'll be good to go. (assuming you are SURE you dont need this nic in dns)

http://support.microsoft.com/kb/188001 <-- if you wanna read about the browser service.

Ahriakin

As a DC it will re-register it's service records regardless of the normal DNS registration setting. There are a number of steps involved in manually changing how it does so.
This is one of the main reasons Microsoft highly recommend you do not Dual-home a DC.

Master browser issues do come into play if that DC is also your WINS server if you are using NetBIOS/WINS for browsing the network and the NICs are on 2 different subnets. Your WINS service may bind to the 2nd NIC and without a WINS proxy in place in the primary to accept and forward broadcasts you're sol.

jkstech

yes, i'm afriad it is a DC, it's not a WINS server and we still need the second nic as it provides a connection to a subnet that we still use.

I know it's got to be something very involved because i've been looking all over off and on for at least a month and haven't found anything........

got a link to that google article or what search string you used to bring it up?