Summary: After build, the ESXi nodes and service VMs use the vCenter as a DNS server even if the customer during the build specified external DNS servers
| Issue | VxRail: After the VxRail build, how do we ensure the external DNS server is being used by the appliance Customer wants to make sure the external DNS server set on build is being used by the appliance |
| Cause | |
| Resolution | When building a VxRail appliance using internal vCenter, nodes and service VMs are expected to the point to vCenter as a DNS server. During the build, vCenter is also configured as DNS server with all the records needed for the appliance to work properly. The DNS on the vCenter server, forward queries that cannot resolve to the external DNS that was configured during the build. When the appliance scales out, the DNS on vCenter will be automatically updated with a new record for the node. If it is required to change the external DNS server, the only change that is needed is on the dnsmasq (forwarder) on the vCenter server. The following KB explain the steps: KB492132: VxRail: How to modify the DNS server IP address for VxRail |
| Notes | This KB only applies to VxRail 4.0 and below release. |