Quantcast
Channel: VMware Communities : All Content - vSphere Upgrade & Install
Viewing all articles
Browse latest Browse all 3263

New cluster with VCSA 6.5 FQDN and DNS doubts

$
0
0

Hello,

I got 3 hosts and I wish to build a vSan cluster for hosting 5 different LANs that have own DC, SQL, Exchange servers and clients to centralize 5 different offices (with own LAN, AD/DC and private domain) on a server farm.

The only things that remain at offices are the printers and a Horizon View client for each user.

 

In past (vSphere 5.0/5.1), I've build a cluster in HA with 2 hosts and another physical box for vCenter server and a DHCP/DNS server for ESXi, iSCSI storage and VDR backup on NAS.

All works good and I have all devices managed with their FQDN.

 

Now the things are different and the Best practice wants VCSA 6.5 and not a physical vCenter server.

But a DNS with PTR and A record is required for installing VCSA 6.5 to have a FQDN for itself and for esxi hosts (and I presume for other appliance like Replication).

If it is all virtual and I need to build a VM (bind on Linux, maybe?) that acts a DNS server, will I go to a chicken-egg problem when I need to power off and power on the entire infrastructure?

 

Or do I need a public domain (like something.com) and put each private IP of ESXi, vCSA as A record of this domain?

I saw many blogs and site with esxi hosts that have a FQDN with .com, but I don't want to use public IPs for all vSphere infrastructure

 

Last, but not least: do I need to replace the selfsigned cert on ESXi and vCSA with a legit one (like lets encrypt)?

 

I'm sorry for my english and I hope anyone may help me


Viewing all articles
Browse latest Browse all 3263

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>