Server 2016 reverse dns not updating
Note: The configurations assume use of ISC's DHCP verion 4.x unless otherwise noted.
However, it should be noted that the order of clauses is not important and should reflect that which makes most sense for the user.# zone clauses are optional and required # only to define params for DDNS # may be one or more zone clauses zone # key clauses are optional # required only for DDNS TSIG # may be one or more key clauses key key-name # must be at least one subnet clause # in a file subnets d.d.d.d netmask d.d.d.d # other clauses may exist, for example, group # which have no relevance for DDNS configuration # and are not shown All the following configurations use the private IPv4 Address (RFC 1918) 192.168.2.254/24 range and example.com, example.net, conventions for boring, but safe, reasons.IPv6 Addresses use the non-routable documentation address 2001:db8::.The DHCP client can signal its intention to perform a DDNS update (to either or both the forward and reverse files) to the DHCP server by using the FQDN option in the DHCPDISCOVER/DHCPREQUEST message (RFC 4702).These transaction types are not discussed further other than where they are relevant to DHCP configuration statements.The lease time in effect says how long the PC/Server may retain the IP address before it must request another one or renew its lease.
Because the IP addresses are being allocated dynamically by the DHCP server, this poses a problem for any DNS configuration which needs to keep track of both the forward map (name to IP address) and possibly the reverse map (IP address to name).
We all know that IP addresses can be spoofed, however, depending on the likelihood of external penetration (or the risk of local rogue machines) it may be a perfectly reasonable solution for, say, home networks or even those sitting behind a NAT gateway or Firewall.
Security is always a judicious blend of paranoia versus real threat.
Transactions 5 and 6: show an alternative method of providing the same DNS update service directly from the DNS client.
This normally occurs in cases where DHCP is not used such as IPv6 using SLAAC though a number of DHCP clients elect to do this even when using DHCP (includes most Windows clients).
Since at this point the PC/Server does not have an IP address is uses the special value 0.0.0.0.