chore: improve hostname documentation for HTTPS usage (#6514)

* chore: improve `hostname` documentation for HTTPS usage

Clarified hostname requirements for HTTPS in meta node configuration.

* Update content/enterprise_influxdb/v1/administration/configure/config-meta-nodes.md

---------

Co-authored-by: Jason Stirnaman <[email protected]>

Author: gwossum

content/enterprise_influxdb/v1/administration/configure/config-meta-nodes.md

@@ -51,6 +51,8 @@ Default is `""`.
 The hostname of the [meta node](/enterprise_influxdb/v1/concepts/glossary/#meta-node).
 This must be resolvable and reachable by all other members of the cluster.
 
+If HTTPS is enabled with [`https-enabled`](#https-enabled), `hostname` must match a hostname or wildcard in the TLS certificate specified by [`https-certificate`](#https-certificate). If `hostname` does not match, then `http: TLS handshake error from 127.0.0.1` errors are output in the meta node logs and the cluster will not function properly.
+
 Environment variable: `INFLUXDB_HOSTNAME`
 
 -----
@@ -152,6 +154,8 @@ Use either:
 * PEM-encoded bundle with both the certificate and key (`[bundled-crt-and-key].pem`)
 * Certificate only (`[certificate].crt`)
 
+When HTTPS is enabled, [`hostname`](#hostname) must match a hostname or wildcard in the certificate.
+
 Environment variable: `INFLUXDB_META_HTTPS_CERTIFICATE`
 
 #### https-private-key