Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a Windows server that is multi-homed (it is NOT a DC). The problem is that the 2nd IP creates a DNS entry as well, which sometimes takes priority over the 1st IP. As such, when somebody tries to connect to a file share on this server by server name it will try to connect to the wrong IP and it won't work.

How would I go about preventing this secondary IP (used for an application, the IP doesn't need to be published in DNS) from creating a DNS entry, while still allowing the primary IP to create an entry?

share|improve this question
up vote 3 down vote accepted

If both ip addresses are bound to the same network card then you won't be able to use the solution Zoredache provided... exactly. What you can do is follow his suggestion and then create a static A record for the ip address that you do want registered in DNS.

share|improve this answer

Are the multiple addresses assigned to a single adapter, or do you have have multiple adapters.

If you have multiple adapters then you should be able to un-check the 'Register this connection's addresses in DNS' box. See

share|improve this answer
I'm would you do it if you don't have multiple adapters? – Windows Ninja Aug 26 '10 at 23:08
@jscott...I meant how to setup the DNS records on a single NIC, but joeqwerty answered that below. Thanks for trying to help out though, I appreciate it. – Windows Ninja Aug 27 '10 at 0:19
This is a great answer and I appreciate it, however the answer below is the answer I was looking for. – ThingsToDo Aug 27 '10 at 11:35

In my case where the server is a domain controller (and I have one address per adapter), unchecking the "Register this connections' address" did not help. I had to put a bogus IP address in the "User the following DNS server addresses" section so when it tried to register the address (despite my telling it not to), no harm was done.

share|improve this answer
More info: you also need to prevent the DNS server from listening to the secondary address. See‌​in-dns/ – Mark Hill Aug 16 '12 at 18:33

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.