Windows 2016 dns records not updating

Those records have an ACL on them to stop registered records from being hijacked by other hosts.

When DHCP is used to allocate IP addresses, the default configuration is shown below—which tells the DHCP server to register records in DNS on behalf of clients only if requested to do so by the client or if the client is unable to dynamically register (e.g., Windows NT 4.0).

However, the reverse DNS entries ("PTR" Records) are not.

This means all DNS records registered by the DHCP servers would be owned by the specified account that is common to all DHCP servers.

Using a credential for the DHCP server doesn't solve the problem of transferring ownership of DNS records for hosts upgrading from NT 4.0; however, this is highly unlikely to still be a concern for organizations today.

i believe it is the 2nd option:" Always dynamically update DNS records." which needs to be selected.

All of the documentation on seeting DHCp to register the records say's that.

Search for windows 2016 dns records not updating:

windows 2016 dns records not updating-53windows 2016 dns records not updating-78windows 2016 dns records not updating-4windows 2016 dns records not updating-11

John, in the image above of the Ipv4 properties you say that the settings are the default settings for DHCP server to register the records on behalf of the client.

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “windows 2016 dns records not updating”