DNS name is a single label hostname with no domain
Event ID 414
Windows 2008 R2 Domain Controller DNS Server.
Event ID 414 was being logegd in this server. Computers in the domain were not applying Computer Group Policies. User Policies were successfull however Computer policies were failing. Using the GPUPDATE /F for foring GPO updates did not work. Removing the computer from the domain and then re-adding it to the domain worked but was not a good fix for many computers.
The solution was to edit the TCP parameters in the registry on the domain controller/DNS server. In the registry, the domain name key was empty as shown in the image as there may have been a registry corruption.
DNS server machine currently has no DNS domain name
This is the location in the registry as shown in the posted image.
Use the Registry Editor to remove hostname and domain name entries and then re-create the registry entries. I renamed the original entries and then created new ones. Once successful, the renamed “bad” keys can be removed. If you prefer, make a backup of the registry entries before editing.
This was done on a live domain controller DNS server. There was no impact on users and this did not require a reboot. There was another domain controller on the network for users and computers to use while this process was taking place.
1. Delete (rename) Hostname, Domain, NV Domain, and NV Hostname.
2. On the Edit menu, point to New, and then click String Value. Re-create each of the entries.
3. Modify the value for each of the entries and add the hostname and doamin name respective for each key.
4. Restart the Net Logon service.
5. Restart the DNS server service. You will no longer see Event ID 414.
6. In the DNS console, go through each of the sections and add the domain name part of the server name whereveer it is missing. The full full fqdn name of the server will now remain and not get changed back to just the server’s hostname.