Dhcp not updating reverse ptr record
The solution provided below is a suggested solution to automate the process using a Power Shell startup script in Active Directory Group Policy (GPO) Power Shell v3.0 is required for the script to complete work on Win2008R2.
I also attached a VBScript version for those who would rather use VBScript then update all the Win2008R2 systems to Power Shell V3.
I think I had trouble with DNS in the past when installing with AD, should perhaps it be installed BEFORE installing AD?
I was asked to setup an infrastructure in Azure Iaa S for a legacy application that requires IPv4 reverse DNS lookup (Limited to the Iaa S environment).
This can have adverse affects with regards to the proper running of your network.
Second, if your server goes down I would assume that your users inability to get to the internet would be the least of your worries, especially since this is a Domain Controller.
However should this be ticked, because if it is ticked it is the client updating the records, where by if it is not ticked would it not be the server that does the update and then manage the connections? Correct , but if the DNS server has some default refresh intervals : DHCP Clients : 24 hours The DHCP Client service sends dynamic updates for the DNS records.
This includes both computers that obtain a leased Internet Protocol (IP) address by using Dynamic Host Configuration Protocol (DHCP) and computers that are configured statically for TCP/IP. So what you say would mean that after the lease period the client PC is not the authoritive owner and the server becomes authoritive and then is able to delete the records?
Search for dhcp not updating reverse ptr record:
It is working really well in our forward zone, if I delete a record and then ask the client to request a new IP, it is instant.