DNS Resolution Fails and 15-Minute Network Delay on newly deployed 9.0.5 or 9.0.4 VMware Live Recovery Appliances
search cancel

DNS Resolution Fails and 15-Minute Network Delay on newly deployed 9.0.5 or 9.0.4 VMware Live Recovery Appliances

book

Article ID: 429918

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Newly deployed VMware Live Recovery Appliances may experience a significant delay (approximately 15 minutes) during the initial boot sequence before networking becomes available. Once the appliance is accessible, DNS resolution fails completely.

Users may observe the following:

  • The VAMI (Virtual Appliance Management Interface) displays the correct DNS server configurations.

  • The /etc/resolv.conf file appears empty or does not contain the configured DNS servers.

  • Manual edits to /etc/resolv.conf are lost immediately after a reboot or a restart of the systemd-networkd service.

Environment

VMware Live Recovery 9.x

Cause

The issue is caused by a configuration conflict between the OS-level systemd-resolved service and the symbolic link for /etc/resolv.conf.

By default, the appliance points to /run/systemd/resolve/stub-resolv.conf. In certain deployment scenarios, this stub file fails to populate with the DNS metadata provided by the VAMI/network configuration. Because the OS attempts to reach network resources during boot, the lack of DNS leads to a 15-minute timeout before the timeout threshold is reached and the boot process continues.

Resolution

To resolve this issue, the symbolic link for /etc/resolv.conf must be redirected to the static resolv.conf file, which bypasses the local DNS stub listener.

  1. Log into the VMware Live Recovery Appliance via console or SSH as a user with root privileges.

  2. Remove the existing problematic symbolic link:

    unlink /etc/resolv.conf

  3. Create a new symbolic link pointing to the correct systemd-managed resolution file:

    ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

  4. Restart the networking services or reboot the appliance to verify the fix:

    systemctl restart systemd-networkd

Additional Information

 

  • Persistence: This change ensures that DNS settings remain persistent across reboots, as the OS will now pull directly from the configuration managed by the system rather than the dynamic stub resolver.

  • Verification: After applying the fix, run cat /etc/resolv.conf to ensure your DNS servers are correctly listed.

 

Powered by Wolken Software