Change DNS settings on a vIDM appliance
search cancel

Change DNS settings on a vIDM appliance

book

Article ID: 371733

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

How to update the DNS settings on the VMware Identity Manager (vIDM) appliance.

Note: Aria lifecycle manager (vRSLCM) does not provide a direct mechanism to modify DNS configurations for vIDM.  

Environment

VMware Identity Manager 3.3.x

Cause

  • The DNS configuration of the vIDM appliance is incorrect or outdated, which leads to login issues with the system domain.
  • When accessing the Identity and Access Management tab via the backdoor URL (https://<VIDM-FQDN>/SAAS/login/0), the interface displays a "redirect too many times" error.
    • This behavior indicates an active issue with the appliance's network or DNS resolution settings.
  • DNS changes in the customer's environment (e.g., SDDC workflows) result in the vIDM appliance retaining legacy DNS pointers in its internal configuration files

Resolution

Note: Shutdown vIDM using Aria lifecycle manager and take a snapshot.
It is also supported to stop the vIDM services and shutdown manually if Aria Lifecycle is not accessible for fails to shutdown vIDM.


If the vApp options are disabled please follow the Activate and add category

    1. In the vSphere UI find your vIDM appliance. Shut it down and take a snapshot if you haven’t done so already.
    2. With your vIDM appliance selected, click Configure and click vApp Options.  


    3. In the right-hand pane, scroll down and select vami.DNS.IdentityManager under the Properties heading.


    4. Scroll back up and click Set Value.


    5. In the dialog that appears, enter the new DNS server that you want vIDM to use and click OK.


    6. Scroll down again and check the value has been set.


    7. Power on the vIDM VM.
    8. Once all services have started you’ll be presented with the appliance DCUI.


    9. To confirm the DNS changes have taken effect you can SSH to the server and run cat /etc/resolv.conf to see the new DNS server details.


NOTE: There are some situations where even after step 9 the issue may persist. Please review the following points if this is the case.

  1. If you run through this process and you end up with a red warning on the DCUI advising you that the VAMI config script failed to run, just perform a guest OS restart through vSphere and it’ll come back up OK.
  2. If you followed the steps and the DNS settings do not change as expected, you will need to delete the following file from the vIDM machine before you shut it down:
    1. rm /etc/resolv.conf.bak

Additional Information

After implementing the changes, please validate the DNS entries in the following locations to confirm their accuracy:

1. /etc/resolv.conf
2. /opt/vmware/share/vami/vami_config_net (ensure no incorrect DNS entries are present)
3. /etc/systemd/network/10-eth0-static.network

 

Powered by Wolken Software