This article describes how to update/replace/change the DNS in a full TKGi environment with NSX, including Bosh Director tile and OpsMan VM.
TKGi with NSX
TKGi tile > Networking > Nodes DNS (each IP separated by a comma)Bosh Director tile > Create Networks > expand each configured Network and update the DNS field (each IP separated by a comma)
The above steps will not inject the new DNS configuration to existing TKGi clusters. If you have existing TKGi clusters, then you'll need to apply/update network-profiles with the new DNS entries:
# tkgi update-cluster <cluster-name> --network-profile <network-profile-name>If you want to verify that the new DNS settings have been correctly propagated to your clusters, you can do:
# bosh configs# bosh config <config-id associated to the TKGi cluster>$ bosh config 40Using environment '172.***' as client 'ops_manager'
ID 40Type cloudName service-instance_***Created At 2025-02-17 11:23:19 UTCContent networks: - name: pks-*** type: manual subnets: - range: 172.***/24 gateway: 172.*** dns: - 192.*** - 8.8.8.8 azs: - az1 cloud_properties: name: pks-*** vm_extensions: - name: service-instance-*** cloud_properties: {}
1 config
Succeeded
The above changes will cause a rollout of new nodes in your clusters, both when applying changes in OpsMan and when updating the existing clusters with the "tkgi update-cluster" command.
To update the DNS entries in the OpsMan VM, from vCenter:
Note: To update the DNS in NSX, please open a Support Request with the NSX team to get proper guidance.