Server 2016 reverse dns not updating
To verify that the primary name server has registered an NS record, type the following: set type=ns If your server is configured correctly, you see an NS record for the name server.Make sure that the authoritative name server listed in the NS record can be contacted to request queries by typing the following: server Next, query the server for any name for which it is authoritative.The following sections describe tests that you can perform to verify that your DNS server is working properly, that the forward and reverse lookup zones are properly configured, and that DNS can support Active Directory.If you use either the Configure DNS Server wizard or the Active Directory Installation wizard to install your Windows 2000 DNS server, most configuration tasks are performed automatically and you can avoid many common configuration errors, but you might still want to perform the tests in this section.Is there a way to update the DNS entry from this server so I don't have to log into my DNS server?
(For more information about Event Viewer, see "Troubleshooting Tools" earlier in this chapter.) Otherwise, you see a list of all the records in the domain.
A reverse lookup zone must exist for each subnet, and the parent reverse lookup zone must have a delegation to your reverse lookup zone.
For example, if you have a private root and the subnets 1.x and 1.x, the private root can host all reverse lookup zones, or it can contain the reverse lookup zone 172.32.x and delegate the reverse lookup zones 1.x and 1.x to other servers.
You can also use Nslookup to verify that the reverse lookup zones and PTR resource records are configured correctly.
To make sure your reverse lookup zones and PTR resource records are configured correctly When you use third-party DNS servers to support Active Directory, you can verify the registration of domain controller locator resource records.