Update dns-records.mdx (#19413)

* Update dns-records.mdx

The SSL Coverage limitation seems to work fine on first level subdomains with Universal SSL and Full setup.
I understand that limitation happens with Universal SSL and Partial setups, when we have to issue a new certificate for each proxied hostname. I added "Partial setup" with the intention of making it more detailed.

* Update dns-records.mdx

---------

Co-authored-by: Nic <[email protected]>

Author: vianaedson

src/content/docs/load-balancing/load-balancers/dns-records.mdx

@@ -60,7 +60,7 @@ If you already have an existing `A`, `AAAA`, or `CNAME` record, be aware that th
 
 ## SSL/TLS coverage
 
-Due to internal limitations, Cloudflare [Universal SSL certificates](/ssl/edge-certificates/universal-ssl/) do not cover load balancing hostnames by default. This behavior will be corrected in the future.
+Due to internal limitations, on [Partial (CNAME) setup](/dns/zone-setups/partial-setup/) the Cloudflare [Universal SSL certificates](/ssl/edge-certificates/universal-ssl/) do not cover load balancing hostnames by default. This behavior will be corrected in the future.
 
 As a current workaround for a domain or first-level subdomain (`lb.example.com`), create a [proxied `CNAME`/`A`/`AAAA` record](/dns/manage-dns-records/how-to/create-dns-records/) for that hostname.