We have our domain controllers acting as on prem DHCP servers, and set to register DNS entries as part of the DHCP process.
I have found today that, for at least some of our remote VPN users, their DNS entries are not updated to their VPN IP, if they had previously been assigned a DHCP address whilst on site.
Even though their DHCP lease is 6 hours, the DNS entry for that lease stuck around.
Even though the security on the DNS entry says SELF is allowed to update, it fails to do so when they connect via the VPN, even though register in DNS is ticked on the VPN connection settings.
I manually deleted the DNS entry for the on prem IP, and a replacement with the VPN IP immediately appeared.
Can anyone suggest why the VPN DNS registration is failing in this scenario?
Cheers
James