Windows server 2016 dns not updating
The DCPromo of a Windows Server 2016 server isn’t really DCpromo any longer as it wasn’t in 2012, but it seems like we all still affectionately call it that for a point of reference.
Active Directory Domain Services is installed the exact same way in Windows Server 2016 through the Server Manager Add Roles wizard. It brings up the features informational box letting you know the additional features that will be installed with the role selected.
Let’s take a look at how to prepare Active Directory Windows Server 2016 DC Adprep and what steps are involved to introduce the first Windows Server 2016 into an existing environment.
If you are interested in an in place upgrade of Windows Server 2016 R2, check our post here.
I am running a Windows 2008 R2 domain with Active Directory integrated DNS.
All users have laptops and frequently switch from wired to wireless connections (these are on separate VLAN's).
This is mainly due to FRS being completely deprecated which is the replication service used to replicate SYSVOL contents.
After the role complets, the wizard will tell you that additional configuration is needed to complete the promotion of the server to be a domain controller.I will monitor the issue for a few days and update status as it progresses Sounds like you may have stumbled onto your issue -- that is, your AD integration means that your DHCP server is letting your DNS server know each time it assigns a lease.Since when you log off the wireless, you're NOT actually releasing the address, the DNS server is keeping that address -- as you have pointed out, for the term of the DHCP lease, or 7 days. you need to setup Dhcp advanced DNS options to Always dynamically update DNS A and PTR records Also you must set credentials in DHCP server properties, other wise this process will not work This will ensure that when DHCP lease will expires \ changes by any mean on DHCP server, it will update corresponding DNS records Also you need to set DNS scavenging in such a way that no-refresh interval must be set to (half) less than refresh interval This will keep DNS server open for accepting dynamic update more time Also ensure that secure dynamic update is enabled on DNS zone Check below article to understand scavenging process correctly and to identify its relation with DHCP To setup scavenging Mahesh I had the dynamic update and DHCP credentials already in place.For the zone in question i have refresh interval of 15 minutes, retry 10 minutes, expiration 1 day, TTL 1 hour. I had most of that in place but did find the DHCP lease time for the wireless scope was set to 7 days and Name Protection was not enabled.I have set this to match the wired scope for lease of 1 day and Name Protection enabled.
After logging back in as an enterprise administrator on the domain, the replicate from domain controller part of the wizard was error free.