When administrators want to edit the DNS settings and select which DNS server to use for vCenter server.
Prerequisites prior to changing the DNS IP for vCenter server.
Changing the DNS server using the VCSA VAMI
https://<vCenter_IP/FQDN>:5480
"I acknowledge that I have made a backup of my vCenter Server and unregistered extensions before continuing with my network configuration"
Next Steps
After network settings have been reconfigured and your vCenter Server Appliance is up and running, additional actions will be required.
All deployed plug-ins will need to be re-registered.
All custom certificates will need to be regenerated.
vCenter HA will need to be reconfigured.
Hybrid Link with Cloud vCenter server has to be recreated.
Active Directory will need to be rejoined.
Note: The Next Steps are applicable only if you are making significant changes like Hostname and vCenter IP Address change. They are not applicable in this case because we are changing only the DNS Server IP Address/es
Sometimes, the vCenter will not start after changing DNS servers and encounter an error message “No healthy upstream
” when connecting with a browser.
Another error message may appear as: "Service did not set the task state
"
If the vCenter Appliance is using an IP address as the hostname, an error may appear as: "Specified hostname is invalid"
If you are unable to update the DNS configuration via the VAMI, it can be changed via command line. See below:
Current Solution:
Changing the DNS server using DCLI:
appliancesh
dcli com vmware appliance networking dns servers get
(Note: The [email protected]
credentials will be required when the command prompts for username and password)dcli com vmware appliance networking dns servers set --mode is_static --servers #.#.#.# --servers #.#.#.#
(Note: To enter multiple entries, the --server flag must be attached multiple times. Running the command again will just overwrite the existing values)
Legacy Solution:
Changing the DNS server using the VAMI_CONFIG_NET
/opt/vmware/share/vami/vami_config_net