vSphere Replication UI Summary page hangs after changing Replication appliance hostname

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• vSphere replication server is "Not accessible " in vCenter UI.

• The hostname of vSphere Replication appliance was changed from IP to FQDN. 

• Cannot open vSphere Replication VAMI on Summary page or reconfigure the appliance from the VAMI page.

http://127.0.0.1:9286/sdk invocation failed with "java.net.SocketTimeoutException: 30,000 milliseconds timeout on connection http-outgoing-5 [ACTIVE]"

• In /var/log/vmware/dr-config.log you may see similar messages.

2025-07- 18T07:18:03.423Z warning drconfig[01127] [SRM@6876 sub=IO.Connection opID=########-####-####-####-##########-isReconfigureRequired] Address resolution took too long; <resolver p:0x00007f199800ff30, '#####################:443', next: (null)>, async: true, duration: 8009msec

Environment

vSphere Replication 8.x

Cause

This issue is caused due to the Incorrect/Invalid/Missing DNS server entries for the vSphere Replication appliance and the vCenter.

The vSphere Replication appliance could not resolve the FQDN of the vCenter Server.

Resolution

Ensure the vSphere Replication can resolve (nslookup) the vCenter FQDN  

- Verify the DNS server address is correct for both vSphere Replication and vCenter server.
- Verify the DNS server records are correct for both vSphere Replication and vCenter server.

• Enable SSH from the appliance VAMI.
• Execute the following command to update the proper DNS

Get the list of DNS servers.
netmgr dns_servers --get

Set the DNS mode (DHCP or static) for one or more DNS servers (comma-separated list).
netmgr dns_servers --set --mode <dhcp|static> --servers <server1,server2,...>

Add a DNS server to the list of DNS servers.
netmgr dns_servers --add --servers <server>

Remove a specified DNS server from the list of DNS servers.
netmgr dns_servers --del --servers <server>

To override DNS, add the vCenter record to the vSphere Replication /etc/hosts file.