Use this procedure to update the DNS server information that you provided during Cloud Foundation bring-up.

Cloud Foundation uses DNS servers to provide name resolution for various components in the system. You must provide root DNS domain information. Optionally, you can provide subdomain information. When you update the DNS server configuration, Cloud Foundation updates the components in a specific order:
  • Platform Services Controllers
  • SDDC Manager
  • vCenter Servers
  • ESXi hosts
  • NSX Managers
  • NSX-T Managers
  • vRealize Suite Lifecycle Manager
  • vRealize Log Insight
  • vRealize Operations
  • vRealize Automation
If the update fails, SDDC Manager rolls back the DNS settings for the failed component. Fix the underlying issue and retry the update starting with the failed component.
Note: There is no rollback for the vRealize components. Check the logs, resolve any issues, and retry the update.

Updating the DNS server configuration is a disruptive process and can take some time to complete, depending on the size of your environment. Schedule DNS updates at a time that minimizes the impact to the system users.

Prerequisites

  • Ensure that both forward and reverse DNS resolution is functional for each component using the updated DNS server.
  • All Cloud Foundation components must be in an Active state.

Procedure

  1. Using SSH, log in to the SDDC Manager VM using the vcf user account.
  2. Get the current DNS server configuration information. 
    curl localhost/inventory/system-info | json_pp
  3. Validate the new DNS server configuration information. 
    curl -H 'Content-Type: application/json' -X POST http://localhost/system/configurations/dns-servers/validator -d '{"dnsServers":[{"server":"<dns-server-ip>","isPrimary":"true"}]}' |json_pp
    Replace <dns-server-ip> with the IP address of the new DNS server. Specify true or false for isPrimary, depending on whether or not the new DNS server is the primary DNS server.
    The validator verifies forward and reverse name resolution for Cloud Foundation components using the new DNS server.
  4. Monitor the status of the validation task. 
    curl http://localhost/operationsmanager/system/configurations/dns-servers/validator/status | json_pp
  5. Check the result of the validation task. 
    curl http://localhost/operationsmanager/system/configurations/dns-servers/validator/result | json_pp
    If validation succeeds, you can proceed to change the DNS server configuration. If validation fails, correct any issues and try again.
  6. Change the DNS server configuration information. 
    curl -H 'Content-Type: application/json' -X POST http://localhost/system/configurations/dns-servers -d '{"dnsServers":[{"server":"<dns-server-ip>","isPrimary":"true"}]}' |json_pp
    Replace <dns-server-ip> with the IP address of the new DNS server. Specify true or false for isPrimary, depending on whether or not the new DNS server is the primary DNS server.
    Note the <id> that gets returned.
  7. Track the status of the DNS update. 
    curl http://localhost/operationsmanager/workflows/<id> | json_pp
    Replace <id> with the ID from the previous step. Wait for the task to complete.
  8. Verify that the DNS configuration was updated. 
    curl localhost/inventory/system-info | json_pp