Users are unable to log into the vSphere Client (UI) using [email protected] or any integrated Active Directory accounts.
root account.vCenter 8.0
This issue is typically caused by a DNS resolution failure. vCenter Server 8.0 relies heavily on Reverse Lookup (PTR) and Forward Lookup (A) records to validate Service Principal Names (SPN) and SAML tokens during the SSO handshake.
The vCenter is unable to resolve its own Fully Qualified Domain Name (FQDN) or IP address.
The configured DNS servers are unreachable or the records have been deleted/modified.
Recent network changes or DNS migrations have left the vCenter with stale DNS pointers.
Log in to the vCenter Server Appliance (VCSA) via SSH using root credentials.
Launch the shell by typing shell.
Test forward and reverse lookup:
# Test Forward Lookup
nslookup <vCenter_FQDN>
# Test Reverse Lookup
nslookup <vCenter_IP_Address>
If either command returns ** server can't find... or connection timed out, DNS is the root cause.
If the DNS servers are incorrect or need to be updated to a working secondary server:
Run the VAMI network configuration tool:
/opt/vmware/share/vami/vami_config_net
Select Option 4 (DNS).
Update the Primary and/or Secondary DNS server IPs to valid, reachable servers.
Exit the tool and restart the vSphere UI service to clear cached sessions:
service-control --restart vsphere-ui
Contact your Internal Network/DNS Team to:
Ensure A records and PTR records for the vCenter exist on the DNS server.
Confirm that firewall rules allow traffic over Port 53 (UDP/TCP) between the vCenter and the DNS servers.