Dns forward lookup zone not updating server 2016

12 Apr

If I run ipconfig /registerdns from any of the clients. There is no error any of the event logs (server or local) and the static entry in forward never updates. I noticed on each record that there is an account called Self with special permissions, yet when you drill down there are none set.

If I restart the machine, it still does not update. I hate to have to delete all this suff in forward, because I am not sure which items actually need to be static.

If the TCP/IP settings for a member computer specify the IP address of a public DNS server—perhaps at an ISP or DNS vendor or the company’s public-facing name server—the TCP/IP resolver won’t find Service Locator (SRV) records that advertise domain controller services, LDAP, Kerberos and Global Catalog.

Without these records, a member computer can’t authenticate and get the information it needs to operate in the domain.

In plain speak, this is when the domains that will be served by this DNS server will be configured.

For the purposes of providing the reader enough knowledge to get this task completed, this article takes a walkthrough approach.

Yet, as you’ll see in this article, most of these issues don’t require extensive diagnostic work or sophisticated tools to isolate and resolve.

As we know that DNS is used for name resolution, it resolves host name to IP address and IP address to host name.

Forward lookup zone is used to resolve Hostname to IP Address, it automatically gets installed and configured in Domain Controllers but we have to install DNS and configure Forward Lookup zone for Member Servers.

In addition to that we also need to install and configure Reverse DNS lookup if we want IP Address to Name resolution to be working.1.

To configure Forward Lookup zone on Windows Server 2012 R2 DNS Server, click on Start button, select the down arrow and select DNS. It can also be open by typing “dnsmgmt.msc” in run or in command prompt.2. Right click Forward lookup and select “New Zone”.3.