"Hostname was not updated via dns reverse-lookup" configuration failure during initial power up of a Cloud Director Appliance

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:

• Deploying a Cloud Director Appliance from OVA and powering it on for the first time.
• 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.

Environment

VMware Cloud Director 10.x

Resolution

To resolve this issue in Cloud Director check the configuration using the steps below:

1. 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.
2. Check that NSX Spoofguard has been disabled before the first power on of the appliance.
3. 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