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?