When building a Windows Server 2016 failover cluster environment in a virtual machine, I encountered the problem of cluster name connection failure, as shown below
The status of the cluster name is "Failed".
Check the cluster events, there are multiple error events-the cluster resource "cluster name" of the type "Network Name" in the cluster role "cluster group" failed. The error code is "0xcb" ("The operating system cannot find the environment option that has been entered.").
Searching for related keywords in the search engine did not find similar problems.
Later, I checked the official documentation and found a possible answer. Because the failover clusters were built in the domain environment in the past, basically following the configuration steps step by step operation without encountering any problems, so this time it is also configured directly according to the steps, and there are warning messages when verifying the cluster, because of the right and wrong In the domain environment, it is normal to feel a little warning, so I ignored it.
The official document has an important step that I did not do, that is, to set the DNS suffix on the computer (Ensure that each node to be joined to the cluster has a primary DNS suffix).
The setting steps are:
Click "Change" under the "Computer Name" tab in the "System Properties" dialog box.
Click "Other" in the "Computer Name/Domain Change" dialog box.
In the "DNS Suffix and NetBIOS Computer Name" dialog box, set the "primary DNS suffix of this computer", for example, I set "SQLTEST.COM", and then restart the computer. This is done for multiple nodes.
After the nodes have restarted, check the cluster status again, and the cluster name can be online normally.
Before touching the new seemingly simple things, it is necessary to read the official documents