After upgrade to VLR 9.0.4 the appliance is not able to resolve .local domain name.
search cancel

After upgrade to VLR 9.0.4 the appliance is not able to resolve .local domain name.

book

Article ID: 414603

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Post upgrade for VLSR from 9.0.2.x to 9.0.4 the domain .local is failing to resolve on the VLSR appliance.

admin@VLR [ ~ ]$ ping domainname(example:abc.local)
ping: VLR.root.local :Temporary failure in name resolution

Environment

VMware Live Site Recovery  9.0.4

Cause

  • This issue is caused by a DNS resolution failure specific to the .local top-level domain. The appliance operating system adheres to RFC 6762, which dictates that .local domains must be resolved via Multicast DNS (mDNS) rather than standard unicast DNS. This intercepts the query at the local DNS stub listener, preventing the appliance from resolving the ESXi host address through the configured upstream DNS servers.

Resolution

 

NOTE: Take snapshot of the VLR appliance before executing the below steps.

Please execute the below command on the VLSR command line post taking the backup of the resolved.conf file.

cd /etc/systemd
cp resolved.conf resolved.conf_bkp
1. Edit /etc/systemd/resolved.conf
2. Find the line "#DNSStubListener=yes", modify it by removing hash symbol "DNSStubListener=no" to disable the local DNS stub listener, and save the file.
systemctl restart systemd-resolved