Forward lookup zone not updating tree dating
The IP ranges represented by the reverse lookup zones must be assigned to your organization, typically by your ISP.
To configure reverse DNS for an Azure-owned IP address that's assigned to your Azure service, see Configure reverse DNS for services hosted in Azure.
This is basically why DNS records are not updating.
If that is the case, it is deleted and a new computer object is set up when joining the PC to the domain.The following example walks you through the process of creating a PTR record in a reverse DNS zone in Azure DNS.For other record types and to modify existing records, see Manage DNS records and record sets by using the Azure portal.For more information, see Import and export a DNS zone file using Azure CLI.For more information on reverse DNS, see reverse DNS lookup on Wikipedia.