Update deploy-manage/deploy/cloud-enterprise/ece-wildcard-dns.md

Author: kunisen

deploy-manage/deploy/cloud-enterprise/ece-wildcard-dns.md

@@ -33,7 +33,7 @@ Additionally, if you use custom endpoint aliases, you must configure a wildcard
 
 ## Wildcard DNS certificate vs static SAN certificate
 
-In {{ece}}, each deployment generates multiple DNS entries, as every component within a deployment has its own cluster ID and fully qualified domain name (FQDN). In environments with many deployments, especially when deployment aliases are used, this can result in hundreds of unique FQDNs that need to be covered by the certificate.
+In {{ece}}, each deployment generates multiple DNS entries, as every component within a deployment has its own cluster ID and fully qualified domain name (FQDN) and can have a second DNS entry using [its alias](./enable-custom-endpoint-aliases.md). In environments with many deployments, especially when deployment aliases are used, this can result in hundreds of unique FQDNs that need to be covered by the certificate.
 
 For this reason, using a wildcard DNS certificate is recommended over a certificate with static SAN entries, as it provides a more scalable, performant, and operationally safe solution.