Changing the domain name for ESXi, vCenter Server, SRM, and VR when hostname and IP remain unchanged in both Production and DR sites
search cancel

Changing the domain name for ESXi, vCenter Server, SRM, and VR when hostname and IP remain unchanged in both Production and DR sites

book

Article ID: 414116

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

In some environments, administrators may need to change the domain name of all vSphere components — including ESXi, vCenter Server, Site Recovery Manager (SRM), and vSphere Replication (VR) — in both Production and DR sites, while keeping the hostname and IP address unchanged.

This article describes the correct sequence, dependencies, and reconfiguration requirements for such domain name changes.

Prerequisites:

  • Before making any change, ensure that the DNS server has already been configured with the new domain name entries.
  • The IP address and hostname of each component remain unchanged throughout the process.
  • Confirm that both forward and reverse DNS lookups resolve correctly for the new domain name.

Environment

  • Two vSphere sites: Production and Disaster Recovery (DR)
  • Each site includes:
    One vCenter Server
    Multiple ESXi hosts managed by the vCenter
    One Site Recovery Manager (SRM)
    One vSphere Replication (VR)
  • Only the domain name changes
  • Hostname and IP address remain the same.
  • SRM and VR are already paired between Production and DR sites.

Resolution

Quick Summary

  1. Perform the change site by site (Production first, then DR).

  2. Within each site, follow this sequence:

    • Step 1 – ESXi

    • Step 2 – vCenter

    • Step 3 – VR

    • Step 4 – SRM

     

  3. After each domain name change:

    • Reconfigure components that were registered to vCenter (SRM and VR).

    • During VR/SRM reconfiguration, ensure "Local host" is updated to the new FQDN.

  4. After both sites are updated:

    • Verify SRM site pairing and VR remote connection.

 

Detailed Procedure

Step 1 – Change ESXi domain name in Production site

 

Step 2 – Change vCenter Server domain name in Production site

  • Change the domain name via the VAMI page (https://<vcenter>:5480), click Networking in the left pane, and then click the upper Edit button in the right pane.

  • vCenter will reboot automatically after the change.

  • Once it is back online, verify that the vSphere Client is accessible using the new FQDN.

  • SRM and VR registered to vCenter must be reconfigured. To do so, access the 5480 VAMI page of each appliance (SRM and VR respectively) and perform RECONFIGURE.

 

Step 3 – Change vSphere Replication (VR) domain name in Production site

  • Log in to VR VAMI (https://<vr>:5480).

  • Click Network in the left pane, and then click EDIT in the right pane to change the domain name and update the DNS Search Path. The system will apply the change and restart the network services automatically.

  • Click Summary in the left pane, and then click RECONFIGURE in the right pane.

  • In the 3 Name and Extension page:

    • The "Local host" field will show Custom, listing the old FQDN.

    • Select the new FQDN from the dropdown list.

  • Complete the reconfiguration wizard to re-register VR with vCenter.

 

Step 4 – Change Site Recovery Manager (SRM) domain name in Production site

  • Log in to SRM VAMI (https://<srm>:5480).

  • Click Network in the left pane, and then click EDIT in the right pane to change the domain name and update the DNS Search Path. The system will apply the change and restart the network services automatically.

  • Click Summary in the left pane, and then click RECONFIGURE in the right pane.

  • In the 3 Name and Extension page:

    • The "Local host" field will show Custom, listing the old FQDN.

    • Select the new FQDN from the dropdown list.

  • Complete the reconfiguration wizard to re-register SRM with vCenter.

 

Step 5 – Repeat Steps 1 through 4 in the DR site

Step 6 – Verification

After completing all changes on both sites:

  • All ESXi hosts show Connected in vCenter.

  • All web interfaces (vCenter, SRM, VR, and their VAMI pages) are accessible through the new domain name in a web browser.

  • vCenter, SRM, and VR appliances display the new domain name under their summary.

  • SRM site pairing status is Connected.

  • VR remote site connection status is Connected.

  • SSL certificate CN/SAN matches the new FQDN.

  • Forward and reverse DNS resolution works correctly.

Powered by Wolken Software