Error: "Hostname was not updated via dns reverse-lookup. Failing OS configuration phase." configuration failure during initial power up of a Cloud Director Appliance
searchcancel
Error: "Hostname was not updated via dns reverse-lookup. Failing OS configuration phase." configuration failure during initial power up of a Cloud Director Appliance
book
Article ID: 325545
calendar_today
Updated On: 02-22-2025
Products
VMware Cloud Director
Issue/Introduction
After the initial power on, the Cloud Director appliance management user interface (VAMI) shows an error when logging in on port 5480 via a browser:
Configuration Failure
OS Configuration Phase has failed.
Please check the log at /opt/vmware/var/log/firstboot for more details on the failure before redeploying this appliance node.
The /opt/vmware/var/log/firstboot log file on a Cloud Director Appliance shows these errors:
[ERROR] Hostname was not updated via dns reverse-lookup. Failing OS configuration phase. [ERROR] Fix and verify DNS server info and other related networking settings, and redeploy this appliance again.
Deploying a Cloud Director Appliance from OVA and powering it on for the first time.
Environment
VMware Cloud Director 10.x
Cause
This issue can occur if the Network Configuration Requirements for VMware Cloud Director have not been met.
Resolution
To resolve this issue in Cloud Director check the configuration using the steps below and redeploy the Appliance OVA:
Ensure that the host names that you specify during installation and configuration of the Cloud Director Appliance OVA are resolvable by DNS using forward and reverse lookup of the fully qualified domain name or the unqualified hostname. This is a requirement as per the Cloud Director documentation, Network Configuration Requirements for VMware Cloud Director.
For example if the Cell's FQDN was "vcd-cell1.example.com" with an IP "192.168.1.2" we would check the following are both successful:
Example forward lookup: nslookup vcd-cell1.example.com
Example reverse lookup: nslookup 192.168.1.2
Check that NSX Spoofguard has been disabled before the first power on of the appliance.
Verify that the proper information was entered for Domain Name, Domain Search Path and Domain Name Servers during the appliance OVF deployment. For example:
Domain Name:vcd-cell1.example.com Domain Search Path:example.com Domain Name Servers:192.168.1.2