How do I prevent one IP from creating a DNS entry on a multi-homed server?

Question

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?

score 7 · Answer 1 · answered Aug 26 '10 at 21:06

7

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 http://support.microsoft.com/kb/305553#6

answered Aug 26 '10 at 21:06

Zoredache

128,755
40
271
413

I'm curious...how would you do it if you don't have multiple adapters? – Windows Ninja Aug 26 '10 at 23:08
@SrSysAdmin: http://serverfault.com/questions/868/multiple-ip-addresses-per-nic – jscott Aug 26 '10 at 23:51
@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 00: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

score 3 · Accepted Answer · answered Aug 26 '10 at 23:11

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.

score 3 · Answer 3 · answered Aug 16 '12 at 15:58

3

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.

answered Aug 16 '12 at 15:58

Mark Hill

31
1

More info: you also need to prevent the DNS server from listening to the secondary address. See [http://www.binarywar.com/2010/01/prevent-registration-of-multiple-ip-addresses-in-dns/](http://www.binarywar.com/2010/01/prevent-registration-of-multiple-ip-addresses-in-dns/) – Mark Hill Aug 16 '12 at 18:33

score 1 · Answer 4 · answered Feb 07 '21 at 04:26

I know this is an aged post, however, I ran into this same issue(s) and discovered another resolutions. Correct me if incorrect.

I was not able to overcome the above aforementioned issue of client DNS attempting to resolve via a second IP address on a dual-port NIC (so, same adaptor) in Windows Server 2016 Essentials.

I was able to overcome this issue by following joeqwerty's solution AND the following:

Open DNS Snap-in via Server Manager -> Tools
Right click root Server -> Properties -> Interfaces
Select "Only the following IP addresses" under "Listen on:"
Uncheck the IP address you do not wish to listen on.
Select "Apply" -> "Ok"
Next, under "Forward Lookup Zones" in the DNS Directory tree right click your primary FLZ.
Select "Properties"
Navigate to "Name Servers" tab
Select your Server FQDN
Select "Edit" underneath pane
Select IP address you DO NOT want to "listen on"
Select "Delete" to the right of selection pane.
Confirm delete.
Apply & Save
Restart DNS Service
Confirm via "nslookup {yourServerHostname}"
Should only return singular IP address.

All is well within my forest now.

Hope this helps anyone in the future.

Best, Taylor

`Hope this helps anyone in the future.` It did sir, it did. – dognose May 18 '22 at 12:18 — dognose, May 18 '22 at 12:18

score 1 · Answer 5 · edited Jul 12 '20 at 07:07

1

You can use the SkipAsSource flag when using netsh to add an IP address to an interface:

Netsh Int IPv4 Add Address <Interface Name> <IP Address> SkipAsSource=True

This will prevent registration in DNS regardless of the setting on the interface a whole.

Be careful when using the UI afterwards as it has a habit of resetting it.

edited Jul 12 '20 at 07:07

Glorfindel

1,213
3
15
22

answered Oct 08 '19 at 05:13

Fowl

396
1
4
21

How do I prevent one IP from creating a DNS entry on a multi-homed server?

5 Answers5

Linked