Information2 use cookies to help you have a superior and more admissible browsing experience on our website. Privacy Policy
Loading...
By:
Renaming a host in vCenter is more than changing its display name. A hostname change can affect DNS records, SSL certificates, and third-party integrations such as backup tools. Proper preparation helps prevent connectivity issues and service disruptions in your VMware environment.
This guide covers three methods to rename an ESXi host in vCenter: using the vSphere Client, SSH commands, and the Direct Console User Interface (DCUI), along with essential pre- and post-rename checks.
When administrators search for how to rename a host in vCenter, they may refer to two different changes.
One option is updating the inventory display name, which you can do by right-clicking the host in the vSphere Client and selecting Rename. This only changes the label shown in the inventory and has no effect on the actual ESXi host configuration.
The second is changing the actual ESXi hostname or fully qualified domain name (FQDN). This is a deeper configuration change that affects the host identity and requires updates to related network settings, such as DNS records and certificates.
In most enterprise environments, changing an ESXi host name in vCenter is usually performed to support infrastructure changes, such as adopting new naming conventions, resolving DNS inconsistencies, or moving hosts to a different network domain.
Changing an ESXi host name involves updates across both the network and virtualization layers. A structured preparation process helps prevent configuration mismatches, connection issues, and unexpected service interruptions during the rename operation.
To minimize connection issues and service disruptions, complete the following steps before renaming the host:
ping and nslookup before making any VMware configuration changes. The vSphere Client provides a graphical interface to modify the host identity. This method removes the host from vCenter inventory first, then uses the ESXi Host Client directly to apply the change before re-adding the host under its new name.
Step 1. If the host belongs to a cluster, drag it out of the cluster first, then right-click it and select Maintenance Mode > Enter Maintenance Mode.
Step 2. Right-click the host, select Connection > Disconnect, then right-click again and select Remove from Inventory.
Step 3. Log in directly to the ESXi Host Client at https://<esxi-ip>/ui using the host’s IP address.
Step 4. Navigate to Networking, select TCP/IP configuration, and choose the Default system stack.
Step 5. Click Edit, update the hostname field with the new name, verify the domain suffix, and click Save.
Step 6. Restart the host’s management network services from the Host Client or via SSH to apply the change.
Step 7. Update your DNS server with the new A record before reconnecting the host.
Step 8. In vCenter, right-click the parent cluster or datacenter, select Add Host, enter the new FQDN, and complete the wizard.
Step 9. Verify that a new SSL certificate is generated and update the certificate trust in your monitoring tools.
Administrators who prefer command-line tools can use an SSH session to change the hostname directly on the ESXi host. The preparation steps in vCenter are the same as Method 1.
If the host’s management network runs on a vSphere Distributed Switch (vDS), migrate the VMkernel adapters to a Standard Switch before proceeding. You can migrate them back to the vDS after re-adding the host to vCenter.
Step 1. If the host belongs to a cluster, drag it out of the cluster first, then right-click it and select Maintenance Mode > Enter Maintenance Mode.
Step 2. Right-click the host, select Connection > Disconnect, then right-click again and select Remove from Inventory.
Step 3. Open an SSH client and connect to the ESXi host using its IP address and root credentials.
Step 4. Retrieve the current hostname configuration:
esxcli system hostname get
Step 5. Set the new short hostname:
eesxcli system hostname set --host=NewHostName
Step 6. Set the new fully qualified domain name (FQDN):
eesxcli system hostname set --fqdn=newhostname.domain.com
Step 7. Restart the management network interface to apply the change:
e/sbin/restart_mgmt_interface.sh
Step 8. Update your DNS server with the new A record and PTR record before reconnecting the host.
Step 9. In vCenter, right-click the parent cluster or datacenter, select Add Host, enter the new FQDN, and complete the wizard.
The Direct Console User Interface (DCUI) is a local text-based interface built into every ESXi host. It is the most reliable option when SSH access is unavailable or the host has lost network connectivity.
Step 1. Access the DCUI at the physical console, through an out-of-band management interface such as iDRAC or iLO, or by typing dcui in an active SSH session.
Step 2. Press F2 and enter root credentials to log in.
Step 3. Use the arrow keys to navigate to Configure Management Network and press Enter.
Step 4. Select DNS Configuration and press Enter.
Step 5. Navigate to the Hostname field, clear the existing value, and type the new hostname.
Step 6. Press Esc to return to the Configure Management Network menu, then press Esc again to exit.
Step 7. When prompted to restart the management network, select Yes to apply the change.
Completing the hostname change is only the first step. After renaming an ESXi host, administrators should verify that core services, network communication, and automation workflows continue to operate correctly. These post-rename checks help identify any remaining references to the old hostname and prevent unexpected issues in daily operations.
Even with proper preparation, administrators may encounter issues during the host renaming process. Most problems are related to DNS resolution, certificate validation, storage connectivity, or cached inventory information. Understanding the root cause of these issues helps restore normal operations quickly.
This error usually occurs when the new DNS record is missing, incorrect, or has not fully propagated. Before reconnecting the ESXi host, verify that the new hostname resolves correctly from the vCenter Server environment.
Run a DNS lookup command such as:
nslookup newhostname.domain.com
Confirm that the hostname returns the correct IP address and that forward and reverse DNS resolution are working as expected.
Changing the ESXi hostname may result in a new SSL certificate being generated. If existing management connections do not recognise the updated certificate, communication between systems may fail.
To resolve this issue, review the affected connection settings, refresh the host certificate information, and confirm that the updated certificate is trusted. In environments with certificate-based authentication, ensure that all related configurations reference the new certificate details.
Storage connectivity issues may occur if the iSCSI Qualified Name (IQN) changes after the hostname update. Since the default iSCSI IQN can include the original hostname, storage access configurations may no longer match the host identity.
Check the iSCSI software initiator settings on the ESXi host, confirm the current IQN value, and update the corresponding storage access configuration if required. Then verify that all datastores and storage paths are restored.
In some cases, the vSphere Client may continue displaying outdated inventory information after the rename operation. This is usually caused by cached browser data or delayed inventory updates.
Refresh the browser session, sign out and back in to the vSphere Client, and verify that both the inventory display name and FQDN reflect the updated host identity.
A hostname change is a low-frequency but high-risk operation. Before you disconnect and re-add the host, backing up your VMs and verifying that your backup solution can still reach the environment after the rename are both worth doing.
i2Backup handles both sides of that concern.
For environments where continuous uptime matters beyond the backup window, i2Availability provides real-time replication and automated failover between production and standby hosts, which can reduce exposure during planned maintenance operations like a hostname change.
Q1: Can I rename an ESXi host in vCenter without removing it from inventory?
If you are only changing the display name, you can do so by right-clicking the host in the vSphere Client. Changing the actual ESXi hostname (FQDN) requires disconnecting and removing the host from inventory before re-adding it under the new name.
Q2: Will renaming a host delete my VMs?
Renaming a host does not delete your virtual machines. The VM files remain intact on their datastores, and vCenter registers them again when you re-add the host.
Q3: Do I need to reboot after changing the hostname via esxcli?
A full reboot is not always required. Restarting the management network interface with /sbin/restart_mgmt_interface.sh is usually enough to apply the hostname change. A reboot is the safest option if the host is already in Maintenance Mode, since it ensures all services pick up the new configuration cleanly.
Q4: What happens to the SSL certificate after renaming?
The ESXi host automatically generates a new self-signed SSL certificate using the updated hostname. vCenter and any integrated tools will need to accept the new certificate thumbprint before they can re-establish a trusted connection.
Q5: What if my host is in a vSAN cluster?
Renaming a vSAN cluster node involves additional steps beyond standard Maintenance Mode to avoid disrupting storage availability and object policies. Consult Broadcom’s official guidance on changing the vSAN ESXi host name before proceeding.
Renaming an ESXi host in vCenter is straightforward once you follow the right sequence: update DNS first, remove the host from inventory, apply the hostname change, then re-add using the new FQDN. Skipping any of those steps is where most issues originate.
After the rename, work through the post-rename checklist before closing the maintenance window. SSL certificate trust, iSCSI IQN changes, and backup tool reconnection are the three areas most likely to cause problems if left unverified.
Before making any hostname change in production, take a backup. Info2soft’s i2Backup protects your VMware environment without host-side agents, so there is nothing to reconfigure on the host itself after the rename completes.
