VCF Operations 9.1 deployment fails at Fleet Lifecycle OVA component installation due to DNS server does not support TCP Port 53 traffic.

Products

• VMware SDDC Manager / VCF Installer

Issue/Introduction

• When deploying VCF Operations 9.1 using the Fleet Lifecycle workflow, the task fails during the "Install VCF Operations and VCF Cloud Proxy using Fleet Lifecycle" stage.
• In the SDDC Manager / VCF Installer UI, you observe errors similar to the following:

The Fleet lifecycle 'OVA component installation' task with ID [ID] failed. Internal errors: Failed to deploy VCF Operations node. Check vCenter tasks for errors. 

• On the newly deployed VCF Operations node, the /opt/vmware/var/log/vrops-init.log contains entries indicating a failure to resolve the FQDN via TCP:

INFO [root - set_hostname - reverse_lookup] - STDOUT for the command ['/usr/bin/host', '-w', '15', '-R', '1', '-T', '<VCF Operations IP>']: ;; Connection to <DNS IP>#53(<DNS IP>) failed: socket is not connected.
;; no servers could be reached
WARNING [root - set_hostname - reverse_lookup] - unable to get an FQDN for the <VCF Operations IP> IP address

Environment

VCF 9.1

Cause

This issue occurs because the DNS server or the network path between the VCF components and the DNS server does not support or allow TCP Port 53 traffic.

Resolution

To resolve this issue, ensure that Port 53 (both UDP and TCP) is open and functional between all VCF components (SDDC Manager, VCF Operations nodes, ESXi hosts) and the configured DNS servers.

Perform a forced TCP reverse lookup:
host -T <VCFOps_Node_IP>
This must return the correct FQDN for the deployment to proceed.