DNS server machine currently has no DNS domain name

DNS server machine currently has no DNS domain name

DNS server machine currently has no DNS domain name

This was a domain controller whose records in DNS were showing only the hostname name of the DC/DNS server. The records in DNS did not show the full internal FQDN. For example, the server name was only displayed, not server.domain.local . Computer group policies would not apply to member computers in the domain. Event ID 414 was being logged on to the DNS event log.

The server was a Windows 2008 R2 domain controller with integrated DNS role.  Although this problem is more prevalent with Windows 2003 domain controllers DBNSserver, in this case there is another domain controller on the network to which this server was joined to and promoted to a DC. That other server is a Windows 2003 Windows server.

This was fixed with a simple registry modification that did not even require a reboot. This 100 percent worked for me. Please read here for the steps and details.

Advertisements

vCloud Director 5.5 Changes to DNS Settings Will Not Automatically be Applied to DHCP

Occurs when Changing Static IP Pool DNS server address

vCloud Director 5.5 Changes to DNS Settings Will Not Automatically be Applied to DHCP

vCloud Director 5.5 Changes to DNS Settings Will Not Automatically be Applied to DHCP

vCloud Director 5.5 Changes to DNS Settings Will Not Automatically be Applied to DHCP

This message appears when changing the static I pool DNs setting in vCloud Director Org (tenant) Network

Make any change in the DHCP, to ensure your DNS setting has changed . The change in DHCP can be removed afterwards.