Retain a DNS plan when building a workgroup failover cluster

Source facts

Workgroup clusters use nodes outside an Active Directory domain or forest, but Microsoft still requires DNS. The prerequisites require every node to run the same Windows Server version and remain in a workgroup. Previously domain-joined nodes must also be renamed after leaving the domain to remove cached AD information. The initial configuration includes an identical account on the nodes, trusted-host configuration, and a common primary DNS suffix. Microsoft documentation.

Applicability

Check the intended workload and server release against the supported workload table. Review storage, quorum, credentials, and name resolution as separate prerequisites before deciding that a workgroup design fits the application.

DSE recommendation

Document the node names, DNS suffix, name-resolution ownership, account management, and prior domain membership. Ask the platform owner to review how administrative access will be maintained. Preserve the original node identity and explicitly plan any required rename before starting cluster creation.

Verification

Verify consistent node configuration and resolution of the intended names from every member. Run the documented validation and test the approved workload and maintenance path. Keep workload-support evidence alongside the results, and resolve a node-identity or DNS discrepancy before admitting the node to service.

Official references

Microsoft Learn: Create a workgroup cluster in Windows Server. Source reviewed September 8, 2026.