-1

On my Windows Server 2022 Standard, I have two network adapters.

  1. The physical network card, which has IP 10.0.22.10/24
  2. The OpenVPN virtual WinTun adapter, which has IP 10.0.30.1/24

Note that I am using the netmask 255.255.255.0, not 255.0.0.0.

Beside OpenVPN, the server has the roles DHCP, DNS, and ActiveDirectory.

As soon as someone connects to OpenVPN, then the WinTun adapter will get IP 10.0.30.1. This IP address is added to the DNS Server, so that my hostname resolves to 10.0.22.10 and 10.0.30.1

The problem: The clients in the company network sometimes resolve the servername to 10.0.30.1, and therefore they cannot reach the server, since 10.0.30.1 is bound to the virtual network adapter and not the physical network adapter.

How can I avoid that the IP address of the virtual WinTun adapter gets automatically added to the DNS Server as "Static IP"?

enter image description here

Daniel Marschall
  • 803
  • 4
  • 9
  • 20

1 Answers1

0

I found the answer here: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/unwanted-nic-registered-dns-mulithomed-dc

  1. Under Network Connections Properties: On the unwanted NIC TCP/IP Properties, select Advanced > DNS, and then unselect Register this connections Address in DNS.

  2. Open the DNS server console, highlight the server on the left pane, and then select Action > Properties. On the Interfaces tab, select listen on only the following IP addresses. Remove unwanted IP address from the list.

  3. On the Zone properties, select Name server tab. Along with FQDN of the DC, you'll see the IP address associated with the DC. Remove unwanted IP address if it's listed.

Daniel Marschall
  • 803
  • 4
  • 9
  • 20