Dynamic DNS is a feature that allows hosts to register their records in DNS, thus removing the need for administrators to manually create records.
However, in Technical Preview 5, Microsoft has re-added the ability to administer Nano Server locally through Power Shell.
According to Microsoft engineer Jeffrey Snover, Nano Server has 93% lower VHD size, 92% fewer critical security advisories, and 80% fewer reboots than Windows Server.
For client computers to be registered and updated dynamically with a DNS server, either: By default, computers attempt to register and perform dynamic update of their DNS names and IP addresses with a DNS server.
For other types of computers, you can deploy Windows Server 2008 DHCP servers, which can perform proxied registrations and updates as needed for nondynamic clients.
You can use the ipconfig /registerdns command option to manually force a retry of the client computer's dynamic registration.
For computers running earlier versions of Windows, you can use the options of the ipconfig command to verify, view, or renew the client TCP/IP configuration details as appropriate.Those records have an ACL on them to stop registered records from being hijacked by other hosts.When DHCP is used to allocate IP addresses, the default configuration is shown below—which tells the DHCP server to register records in DNS on behalf of clients only if requested to do so by the client or if the client is unable to dynamically register (e.g., Windows NT 4.0).What this means in practice is the following: This means the DHCP server computer account will own certain records in DNS, such as the PTR records and even some A records for older hosts.(However, it's unlikely that you would have many NT 4.0 hosts in your environment.) This can cause the following two problems: For this reason, DHCP servers could be added to a group called Dns Update Proxy.Just let it ride until you're seeing id 2501 events in the DNS Server event logs.