Dns forward lookup zone not updating server 2016
A Windows Server 2016 service, known as the Domain Name System (DNS) server role, resolves these names into IPv4 or IPv6 addresses.
Since many important apps and services rely on the DNS server role, it is important that you know how to install and configure Windows Server 2016 name resolution using the DNS server role.
For the purposes of providing the reader enough knowledge to get this task completed, this article takes a walkthrough approach.
A DNS server has been installed but not yet configured at the beginning of this article and we’ll create the forward and reverse lookup zones using the built-in wizard.
If you find that you can not resolve IP’s back to a name on your network check your DNS REVERSE LOOKUP ZONE.
Visit Stack Exchange I've stumbled upon a strange behaviour with Windows machines, which seems to be fairly consistent between all Windows versions from Vista/2008 to 8.1/2012 R2; it doesn't happen instead when using Windows XP or Windows Server 2003.
The problem is this: when the network adapter is configured for DHCP and the DHCP server doesn't register DNS records on behalf of its clients (because it can't, or because it's not configured to do so), then in the TCP/IP settings of the network interface: As much as it may appear strange, this is the only solution to ensure Windows will register both the A and the PTR records for a DHCP network connection; otherwise, it will only register the A record.
I don't have a convenient test environment to try it...
In Windows 2008 and above, there is an option in the DHCP scope to set up the DHCP server to automatically update the authoritative DNS servers with the host (A) and PTR) records of the DHCP clients.Stay tuned for a follow-up article that will review the different available record types and how to configure them.