-DNS server - Win Server 2019 / Microsoft Windows DNS server zone name "zone1" / private IP 10.1.0.5 / hostname "vm" / FQDN "vm.zone1" -Azure Openvpn virtual network gateway provides DHCP details to clients with the DNS server as 10.1.0.5 and 208.67.222.222 -DHCP server does not register the DHCP clients in DNS server hence DNS/DHCP clients will have to manually register in DNS

Remote sites: -All clients are here -Ubuntu, Raspbian, Windows 10 and Windows Server 2019 clients after connecting to openvpn can ping and resolve names successfully from 10.1.0.5 -Ubuntu and Raspbian can even auto register its own address and hostname in DNS server -Windows 10 and Windows server 2019 (hostname "vm3" / primary dns suffix "zone1) have the checkbox "Register this connections addresses in the DNS" as checked for the vpn interface. But still it is not able to register its own address in the DNS server (10.1.0.5). Event id 8016 on all windows client says:

The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings:

   Adapter Name : {806576C3-06F9-466B-A11E-CC73E5071980}
   Host Name : vm3
   Primary Domain Suffix : zone1
   DNS server list :
        10.1.0.5, 168.63.129.16
   Sent update to server : <?>
   IP Address(es) :
     172.16.201.3

The reason the system could not register these RRs was because the DNS server failed the update request. The most likely cause of this is that the authoritative DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress.

You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator.

In the above event all details are correct except "Sent update to server : <?>" why is this "?" it should have been "10.1.0.5". Unless it sends the update to the right IP address the registration will obviously fail.

-Besides ubuntu and Raspbian, even the DNS server itself is able to auto register its ip and hostname in the dns records.

• Tried the registry and group policies in windows clients with default settings and also modifications in : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

-ipconfig /registerdns also gives the same event error

• DNS server - Win Server 2019 / Microsoft Windows DNS server zone name "zone1" / private IP 10.1.0.5 / hostname "vm" / FQDN "vm.zone1"
• Azure Openvpn virtual network gateway provides DHCP details to clients with the DNS server as 10.1.0.5 and 208.67.222.222
• DHCP server does not register the DHCP clients in DNS server hence DNS/DHCP clients will have to manually register in DNS

Remote sites:

• All clients are here
• Ubuntu, Raspbian, Windows 10 and Windows Server 2019 clients after connecting to openvpn can ping and resolve names successfully from 10.1.0.5
• Ubuntu and Raspbian can even auto register its own address and hostname in DNS server -Windows 10 and Windows server 2019 (hostname "vm3" / primary dns suffix "zone1) have the checkbox "Register this connections addresses in the DNS" as checked for the vpn interface. But still it is not able to register its own address in the DNS server (10.1.0.5). Event id 8016 on all windows client says:

The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings:

   Adapter Name : {806576C3-06F9-466B-A11E-CC73E5071980}
   Host Name : vm3
   Primary Domain Suffix : zone1
   DNS server list :
        10.1.0.5, 168.63.129.16
   Sent update to server : <?>
   IP Address(es) :
     172.16.201.3

The reason the system could not register these RRs was because the DNS server failed the update request. The most likely cause of this is that the authoritative DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress.

You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator.

In the above event all details are correct except "Sent update to server : <?>" why is this "?" it should have been "10.1.0.5". Unless it sends the update to the right IP address the registration will obviously fail.

• Besides ubuntu and Raspbian, even the DNS server itself is able to auto register its ip and hostname in the dns records.

• Tried the registry and group policies in windows clients with default settings and also modifications in : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

• ipconfig /registerdns also gives the same event error