System message error updating dns nameserver not registered
The Dynamic Host Configuration Protocol (DHCP) allowed enterprises and Internet service providers (ISPs) to assign addresses to computers automatically as they powered up.
In addition, this helped conserve the address space available, since not all devices might be actively used at all times and addresses could be assigned as needed.
As the system grew this task became difficult for any one site to handle, and a new management structure was introduced to spread out the updates among many domain name registrars.
The tables were maintained manually in form of the host file.
The first is "dynamic DNS updating" which refers to systems that are used to update traditional DNS records without manual editing.
These mechanisms are explained in RFC 2136, and use the TSIG mechanism to provide security.
This feature required that DNS servers be kept current automatically as well.
The first implementations of dynamic DNS fulfilled this purpose: Host computers gained the feature to notify their respective DNS server of the address they had received from a DHCP server or through self-configuration.
This protocol-based DNS update method was documented and standardized in IETF publication RFC 2136 in 1997 and has become a standard part of the DNS protocol (see also nsupdate program).