VCF Operations 9.1 fails to detect License Server due to DNS Resolution

Products

• VCF Operations

Issue/Introduction

• In VCF Operations 9.1, the license server deployment completes on the vCenter , however the newly deployed license server is not detected in the VCF Operations UI.
• On the License server vm console, a status similar to below is observed:
  

Environment

VCF Operations 9.1

Cause

This issue is caused when there is a conflict wrt DNS name resolution for the VCF Operations nodes. In this particular scenario, the VCF Operations node reverse DNS (PTR) entries were not resolving to its IP address, preventing successful name resolution and the network communication required for license server detection

Without correct forward and reverse DNS resolution, the VCF Operations node cannot establish the necessary connections to detect, communicate with, and configure the deployed license server.

Resolution

To successfully allow the VCF Operations to successfully detect the license server and complete the license registration process, follow the below steps:

1. Identify the incorrect DNS entries configured for the VCF Operations node.

2. Update the DNS server records to ensure correct forward (A) and reverse (PTR) resolution for the VCF Operations node.

3. Retry the license server detection and configuration workflow from the VCF Operations UI.

Additional Information

In case the issue still persists, redeploy the License Server on the vCenter by following Newly deployed License Server not showing up under the License Server tab in VCF Operations