hostname format restrictions

Author: ranbel

src/content/docs/cloudflare-one/connections/connect-networks/private-net/cloudflared/connect-private-hostname.mdx

@@ -45,6 +45,17 @@ This section covers how to enable remote access to a private hostname applicatio
 
 ### 1. Connect the server to Cloudflare
 
+Hostname must be unique for an account (1:M mapping from hostname to Tunnel)
+
+	<Details header="Hostname format restrictions">
+			- Less than 255 characters
+			- Leading wildcards (`*`) and dots (`.`) are allowed but trimmed off. For example, `*.internal.local` becomes `internal.local`.
+			- Ending dots (`.`) are allowed but trimmed off.
+			- No wildcards (`*`) in the middle. For example, `foo*bar.internal.local` is not allowed.
+			- Hostnames with non-Latin characters must be Punycode encoded and include the [ACE prefix](https://en.wikipedia.org/wiki/Punycode#ACE_prefix_for_internationalized_domain_names). For example, to represent `例.internal.local`, enter `xn--fsq.internal.local`.
+	</Details>
+
+
 ### 2. Set up the client
 
 <Details header="Feature availability">

src/content/partials/cloudflare-one/access/add-target.mdx

@@ -19,7 +19,7 @@ To create a new target:</p>) :
 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Targets**.
 2. Select **Add a target**.
 3. In **Target hostname**, enter a user-friendly name for the target resource. We recommend using the server hostname, for example `production-server`. The hostname does not need to be unique and can be reused for multiple targets. Hostnames are used to define the subset of targets included in an infrastructure application and are not used in DNS address resolution.
-	<Details header="Format restrictions">
+	<Details header="Hostname format restrictions">
 			- Case insensitive
 			- Contain no more than 253 characters
 			- Contain only alphanumeric characters, `-`, or `.` (no spaces allowed)