Error: FQDN #### cannot be resolved during Management Components Deployment in VMware Cloud Foundation 9.1

Products

• VCF Operations

Issue/Introduction

During the "Deploy VCF Management Components" workflow in VMware Cloud Foundation (VCF) 9.1, the task fails during the pre-deployment validation stage.

The following error is observed in the VCF Operations UI for the sub-task "Prepare input for the deployment of VCF License Server" :

Message: FQDN #### cannot be resolved to an IP address
Reference Token: [Token ID]

Environment

VMware Cloud Foundation 9.1

Cause

In VCF 9.1, the License Server is a mandatory component. The deployment workflow enforces strict pre-flight checks requiring that the hostnames of all new components be resolvable via DNS (Forward and Reverse) before provisioning begins. If the Forward (A) or Reverse (PTR) records are missing, the validation script will fail to prevent partial installations.

Resolution

To resolve this issue, ensure the DNS environment is correctly configured for the new License Server component:

1. Create DNS Records by adding a valid A record (Forward lookup) for the License Server FQDN and a corresponding PTR record (Reverse lookup) for the License Server IP address.
2. Open an SSH session to the SDDC Manager or another management node and run the following command to confirm the FQDN resolves to the correct IP:
   nslookup [License-Server-FQDN]
3. Resume the Task by navigating back to the VCF Operations UI --> Build --> Tasks.

Should the issue still persist, see Contact Broadcom Support.

Additional Information

• Upgrade Sequence and Related Issues for VMware Cloud Foundation and vSphere Foundation 9.1
• Deploy a License Server