VMware Cloud Foundation 3.0 requires an External DNS server. In my lab environment I have a Windows Server 2012 R2 virtual machine that I use a a DNS Server.
If you are only planning on deploying the Management Workload Domain in your nested environment you only need to create the forward and reverse lookup records for Management Workload Domain. If you plan on deploying a Virtual Infrastructure Workload Domain in the future then you will also need to create the Virtual Infrastructure forward and reverse lookup records.
Note: This is the minimum number of DNS Records required. VMware Cloud Foundation does not require DNS Records for NSX Controllers. For a more comprehensive list of DNS Requirements see the VMware Cloud Foundation Planning & Preparation Guide.
| Workload Domain | Name | Type | Data |
| Management | sfo01m01esx01 | Host (A) | 172.16.11.101 |
| Management | sfo01m01esx02 | Host (A) | 172.16.11.102 |
| Management | sfo01m01esx03 | Host (A) | 172.16.11.103 |
| Management | sfo01m01esx04 | Host (A) | 172.16.11.104 |
| Management | sfo01m01psc01 | Host (A) | 172.16.11.61 |
| Management | sfo01m01psc02 | Host (A) | 172.16.11.63 |
| Management | sfo01m01vc01 | Host (A) | 172.16.11.62 |
| Management | sfo01m01nsx01 | Host (A) | 172.16.11.65 |
| Management | sfo01m01sddcmgr | Host (A) | 172.16.11.60 |
| Management | sfo01vrli01 | Host (A) | 172.16.11.10 |
| Management | sfo01vrli01a | Host (A) | 172.16.11.11 |
| Management | sfo01vrli01b | Host (A) | 172.16.11.12 |
| Management | sfo01vrli01c | Host (A) | 172.16.11.13 |
| Virtual Infrastructure | sfo01w01esx01 | Host (A) | 172.16.31.101 |
| Virtual Infrastructure | sfo01w01esx02 | Host (A) | 172.16.31.102 |
| Virtual Infrastructure | sfo01w01esx03 | Host (A) | 172.16.31.103 |
| Virtual Infrastructure | sfo01w01esx04 | Host (A) | 172.16.31.104 |
| Virtual Infrastructure | sfo01w01vc01 | Host (A) | 172.16.11.66 |
| Virtual Infrastructure | sfo01v01nsx01 | Host (A) | 172.16.11.64 |
