How to update Aria Automation DNS property "Domain Search Path "
search cancel

How to update Aria Automation DNS property "Domain Search Path "

book

Article ID: 370826

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

In case you need to update the additional DNS properties like 

DNS property "domains" is mapped as key "vami.domain.vRealize_Automation" in /opt/vmware/etc/vami/ovfEnv.xml

DNS property "domain search" is mapped as key "vami.searchpath.vRealize_Automation" in /opt/vmware/etc/vami/ovfEnv.xml 

Environment

Aria Automation 8.18.x

Cause

All DNS appliance properties is set during the initial Aria Automation deployment search, domains are set during initial appliance deployment

After the deployment, we can change the DNS servers using vracli command as per documentation 

Update the DNS assignment for VMware Aria Automation

Example:

vracli network dns set --servers DNS1,DNS2

But this does not change the other DNS properties like: domain and domain search, to update those you need to follow the steps from the Resolution section.

Resolution

In order to update and validate the DNS properties like: Domain Search Path, please follow the steps:

  1. Login to the Aria Automation Appliance console or ssh as root and stop services.
    /opt/scripts/deploy.sh --onlyClean
  2. Shutdown guest OS using LCM or vCenter.
  3. Update 'vApp Options' in vCenter for all the nodes.
  4. Power on the nodes from vCenter.
    Note: Do not power on from LCM as it will power on the nodes and run deploy script.
  5. SSH into the nodes as root and check the file
    cat /opt/vmware/etc/vami/ovfEnv.xml
    Note: It should reflect the changes done in vCenter, if not you need to manually update the file.
    vi /opt/vmware/etc/vami/ovfEnv.xml
  6. Update the 'Domains & DNS' section in /etc/systemd/resolved.conf.
    vi  /etc/systemd/resolved.conf
    Note: For multiple DNS IP enter the IP address with a space Example: ##.##.##.## ##.##.##.##
  7. Restart 'resolved' service to apply the changes to /etc/resolv.conf and kube-system coredns
    systemctl restart systemd-resolved.service
  8. Check the resolv.conf file to make sure that the new DNS entries are seen.
    cat /etc/resolv.conf

    Note: If the new DNS entry is missing, reboot the appliance.

  9. Run deploy.sh script
    /opt/scripts/deploy.sh

    Note: Wait for prelude pod deployment to complete successfully.