Unable to Access vSphere Replication VAMI Due to DNS Resolution Issues

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

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

• 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 the following warning is observed:

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 9.x
• VMware Live Recovery 9.x

Cause

• The issue is caused by an incorrect or unreachable DNS configuration on the vSphere Replication appliance. As a result, the appliance is unable to resolve the FQDN of the vCenter Server.
• The nslookup command fails with DNS timeout errors.

root@vr_hostname[ / ]# nslookup 10.##.#.##
;; communications error to 172.22.###.###53: timed out
;; communications error to 172.22.###.###53: timed out
;; communications error to 172.22.###.###53: timed out

Resolution

1. Enable SSH from the appliance VAMI.
2. Execute the following command to update the proper DNS
   1. Get the list of DNS servers.
      • netmgr dns_servers --get
   2. 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,...>
   3. Add a DNS server to the list of DNS servers.
      • netmgr dns_servers --add --servers <server>
   4. 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.