vCenter Server 8.0 Upgrade fails with FQDN resolution errors due to PNID and DNS PTR mismatch

Products

• VMware vCenter Server

Issue/Introduction

When attempting to upgrade VMware vCenter Server to version 8.0.3j, the installer GUI halts during the pre-check phase with FQDN resolution errors. This occurs even when forward DNS (A records) appear to resolve correctly.

Primary Product: VMware vCenter Server
Component: vCenter Server Management / Upgrade
Symptoms:
The upgrade installer reports that the FQDN cannot be resolved or does not match the system configuration.
vCenter Diagnostic Tool (VDT) indicates conflicts between the Primary Network Identifier (PNID), the OS hostname, and Active Directory computer objects.
Inconsistent Reverse DNS (PTR) lookups across different DNS name servers.

Environment

• VMware vCenter Server 7.x, 8.x

Cause

The vCenter 8.0 upgrade installer enforces a strict 1:1 match between the System Hostname, the internal Primary Network Identifier (PNID), and the Reverse DNS (PTR) record. The pre-check fails if the appliance is in a "split-brain" identity state, typically caused by:

Assigning a new DNS alias/hostname to the vCenter without performing the official PNID change procedure.
Out-of-sync DNS servers returning conflicting PTR records for the vCenter IP address.
Active Directory computer object names that do not match the current OS hostname.

Resolution

To resolve these identity conflicts and proceed with the upgrade, ensure the vCenter identity is unified across all layers.

Prerequisites:

Take an offline snapshot or file-based backup of the vCenter Server Appliance.
Ensure you have root credentials for the VCSA.

1.) # Test reverse lookup from the vCenter shell
nslookup <vCenter_IP>

2.) Verify Internal Identity (PNID and Hostname): Ensure the internal PNID matches the OS hostname.

# Check PNID
/usr/lib/vmware-vmafd/bin/vmafd-cli get-pnid --server-name localhost

# Check OS Hostname
hostnamectl status

If these do not match the intended FQDN, you must revert the hostname to match the PNID or follow the official documentation to change the PNID before attempting the upgrade.

3.) Address Active Directory Conflicts: If the Active Directory object is mismatched or the GUI is unresponsive, use the CLI to leave the domain:

/opt/likewise/bin/domainjoin-cli leave

4.) Re-join Domain and Run Upgrade: Once the FQDN, PNID, and PTR records are unified, re-join the domain and initiate the upgrade using the original, verified FQDN.

/opt/likewise/bin/domainjoin-cli join <domain_fqdn> <user_name>

 

 

 

Additional Information

• For instructions on changing the vCenter PNID, see KB 71076
• For troubleshooting DNS in VCSA, see KB 406530