Change DNS server settings on a vIDM appliance
| 2 minutes
VMware VMware Identity Manager vIDM DNS OVA

If you’re ever in a position where you need to change the DNS settings on your VMware Identity Manager (vIDM) appliance, you may have noticed that vRealize Suite Lifecycle Manager (vRSLCM) doesn’t provide you with this mechanism. Luckily, the vIDM appliance itself contains “OVF Properties” within the vSphere UI. You can shutdown the appliance and modify these settings to allow the appliance network configuration to re-apply your new configurations to the guest.

Note: Shutdown your vIDM solution using vRSLCM and take a snapshot.

  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.

    vApp Options screen for vIDM

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

    VAMI DNS Property

  4. Scroll back up and click Set Value.

    Editing VAMI options

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

    DNS IP Dialog

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

    Confirm the new IP is set.

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

    Successful boot

  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.

    Resolver file contents

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.

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:

rm -f /etc/resolv.conf.bak
About Stellios Williams
Senior Cloud Solutions Architect VMware
This is my personal tech related blog for anything private and public cloud - including homelabs! My postings are my own and don’t necessarily represent VMware’s positions, strategies or opinions. Any technical guidance or advice is given without warranty or consideration for your unique issues or circumstances.
Comments
comments powered by Disqus
Advertisement