License Server Not Detected Due to DNS Resolution Failures in VCF Operations 9.1
search cancel

License Server Not Detected Due to DNS Resolution Failures in VCF Operations 9.1

book

Article ID: 445428

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

In VMware Cloud Foundation (VCF) Operations 9.1, the license server deployment completes on vCenter Server, but the newly deployed license server is not detected in the VCF Operations user interface.

Symptoms include:

  • The license server Virtual Machine (VM) console displays status as Not configured and Disconnected.

  • When the license server is detected in VCF Operations, stale licenses remain with the following error:

    This license is no longer associated with this VCF Operations instance, but could not be fully removed. To complete the removal, assign a new license to the vCenter instances which have this license assigned to them.

  • Assigning a license to a selected vCenter Server fails with the following error:

    vCenter is unable to resolve the license server host name. Ensure an A record and PTR are added to the DNS servers used by the vCenter.

 

Environment

  • VMware Cloud Foundation (VCF) 9.1
  • VCF Operations 9.1
  • vCenter 9.1

Cause

Functional forward (A) and reverse (PTR) DNS resolution is required for communication with the license server. Mismatched or missing DNS records for the license server, or the failure of the VCF Operations node to resolve its own hostname or IP address, results in license server registration failure.

Resolution

To allow VCF Operations to detect the license server and complete registration:

  1. Validate forward and reverse name resolution using nslookup. Ensure these commands return valid A and PTR records for both the License Server and VCF Operations node:

    nslookup <license_server_hostname>
nslookup <license_server_IP>
nslookup <VCF_ops_hostname>
nslookup <VCF_ops_IP>

  2. Identify any incorrect or missing DNS entries for the VCF Operations node or License Server if nslookup fails to return the expected results.

  3. Update the DNS server configuration to create or correct the forward (A) and reverse (PTR) records.

    • Ensure all DNS records use lowercase characters to prevent case-mismatch resolution failures.

  4. 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:

Powered by Wolken Software