Website under construction

Network name diagnostics 
Windows Server 2016 features improvements related to diagnosing network name problems. At times, 
some of the events are confusing or not even present. For example, previously, problems updating 
DNS resulted in a generic error indicating that DNS could not be updated. But the error notification 
did not indicate why DNS could not be updated. There can be several reasons for this: 

DNS does not accept dynamic updates. 

You are using a secure DNS server, and the cluster does not have the proper rights. 

There are timeouts getting to the DNS server. 

---

39 
CHAPTER 2 | Software-defined datacenter 
Troubleshooting an event such as this took time because you had to look at it in broad terms before 
you could focus on a specific area and narrow down the problem. In Windows Server 2016, events are 
updated to include the specific error. So, if the error is due to one of the reasons mentioned in the list, 
you are notified of the error and can immediately focus on that one cause. This makes for quicker 
resolutions because you do not need to troubleshoot a problem that does not exist. 
Also, additional checks have been added for the network name to help prevent a problem that might 
not occur for days or weeks. During every online/offline of the resource and every one hour that the 
name is online, Windows Server 2016 checks for the following: 

A searchable domain controller 

A synchronized Cluster Name Object (CNO) password 

A CNO in Active Directory that is turned on 

An existing CNO and Virtual Computer Object (VCO) in Active Directory 
Windows Server 2016 also includes several additional tests in cluster validation for network names to 
do the following: 

Check that the CNO and VCO are greater than 15 characters 

Verify that the CNO has Create Computer Object permissions in the Organizational Unit (OU) in 
the Active Directory of which it is a member 

Ensure that it is possible to sign in to the CNO and corresponding VCO 

Confirm that the local Users group on the nodes has the members CLISUR and NT 
AUTHORITY\Authenticated Users 
The previous items are commonly the cause of issues with network names, which is why these new 
diagnostics were added.