WSFC Windows2019 create Computer Account, but not register DNS name.

(0919)小林智之 61 Reputation points
2022-08-22T08:48:21.687+00:00

When building WSFC with two Windows2019 nodes, the Cluster is completed, but the name resolution of the Cluster IP fails.
("Cluster IP" refers to the IP displayed inside the Cluster Core Resource.)

When I checked the resource status in AD, the Computer Account for ClusterIP was created, but the DNS name was not registered.

In previous versions of Windows this was a registered recognition, has the behavior changed?

Also, how can I fix this issue?

Thank you.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,441 questions
0 comments No comments
{count} votes

Accepted answer
  1. Limitless Technology 39,336 Reputation points
    2022-08-23T08:24:31+00:00

    Hello there,

    This behavior is by design. It occurs because NetBIOS no longer binds to IP address resources in Windows Server 2016 or later versions of the Windows Server-based Cluster service.

    To work around this behavior, use the Cluster Management console to determine the name of the IP address resource that must be changed.

    NetBIOS and WINS don't bind to cluster IP address resources https://learn.microsoft.com/en-us/troubleshoot/windows-server/high-availability/netbios-wins-dont-bind-cluster-ip-address-resources

    ----------------------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept it as an answer–

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. (0919)小林智之 61 Reputation points
    2022-08-25T11:06:27.53+00:00

    Thank you for teaching me this link. It seems that the problem is solved.

    0 comments No comments