[DNS] Update proxy status page and improve information overload (#19728)

* Recap what are DNS records, remove image, and add Benefits h3

* Briefly explain the example pointing to Fundamentals for more

* Remove repeated explanation and details on egress IPs

* Repurpose proxied-records h2 and update anchor links

* Add dedicated folder to move proxying higher on the sidenav

* Add dedicated page to proxying limitations

* Add Secondary DNS with pre-signed DNSSEC limitation

* Explicitly call out DNS-only on pre-signed DNSSEC warning

* Replace link to Secondary DNS in limitations.mdx

* Small text tweaks for consistency

* Call out example where CNAME shouldn't be proxied

* Move proxied-dns-records to index.mdx for name consistency

* Adjust pcx_content_type accordingly

* Improve linkning to Fundamentals from limitations.mdx

* Apply PM feedback and improve passive voice

* Edit explanation of predefined TTL as per PM comment

* Fix links with specific anchors to limitations

* Find and replace remaining links that kept valid anchors

* Further adjust specific links to #proxied-records

* Add redirect from previous buried page to new one

* Adding some changes left unstaged

* Fix broken links

* Apply suggestions from code review

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

---------

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

Author: 2 people

public/_redirects

@@ -354,6 +354,7 @@
 /dns/foundation-dns/graphql-analytics/ /dns/additional-options/analytics/ 301
 /dns/manage-dns-records/how-to/dns-load-balancing/ /dns/manage-dns-records/how-to/round-robin-dns/ 301
 /dns/manage-dns-records/how-to/create-root-domain/ /dns/manage-dns-records/how-to/create-zone-apex/ 301
+/dns/manage-dns-records/reference/proxied-dns-records/ /dns/proxy-status/ 301
 /dns/reference/troubleshooting/ /dns/reference/recommended-third-party-tools/ 301
 /dns/zone-setups/partial-setup/convert-partial-to-full/ /dns/zone-setups/conversions/convert-partial-to-full/ 301
 /dns/zone-setups/partial-setup/convert-partial-to-secondary/ /dns/zone-setups/conversions/convert-partial-to-secondary/ 301

src/content/changelogs/rules.yaml

@@ -37,7 +37,7 @@ entries:
   - publish_date: "2024-09-20"
     title: Automatic DNS Validation for Cloudflare Rules
     description: |-
-      The Cloudflare dashboard now automatically validates [DNS records](/dns/manage-dns-records/reference/proxied-dns-records/) and [Cloudflare for SaaS custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) for rules targeting specific hostnames or URLs. To prevent misconfigured rules and ensure smoother deployments, you will get proactive warnings for missing or misconfigured DNS records and custom hostnames.
+      The Cloudflare dashboard now automatically validates [DNS records](/dns/proxy-status/) and [Cloudflare for SaaS custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) for rules targeting specific hostnames or URLs. To prevent misconfigured rules and ensure smoother deployments, you will get proactive warnings for missing or misconfigured DNS records and custom hostnames.
 
   - publish_date: "2024-09-17"
     title: Compression Rules available to all plans with Zstandard support

src/content/changelogs/trace.yaml

@@ -18,4 +18,4 @@ entries:
   - publish_date: "2024-03-12"
     title: Cloudflare Trace now supports grey-clouded hostnames
     description: |-
-      Even if the hostname is [not proxied by Cloudflare](/dns/manage-dns-records/reference/proxied-dns-records/#dns-only-records), Cloudflare Trace will now return all the configurations that Cloudflare would have applied to the request.
+      Even if the hostname is [not proxied by Cloudflare](/dns/proxy-status/#dns-only-records), Cloudflare Trace will now return all the configurations that Cloudflare would have applied to the request.

src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx

@@ -123,7 +123,7 @@ You can periodically check the service binding status using the [List Service Bi
 
 ## 3. Create address maps
 
-Once you have configured your IPs to have CDN service, you can use <GlossaryTooltip term="address map" link="/byoip/address-maps/">address maps</GlossaryTooltip> to specify which IPs should be used by Cloudflare in DNS responses when a record is <GlossaryTooltip term="proxy status" link="/dns/manage-dns-records/reference/proxied-dns-records/#proxied-records">proxied</GlossaryTooltip>.
+Once you have configured your IPs to have CDN service, you can use <GlossaryTooltip term="address map" link="/byoip/address-maps/">address maps</GlossaryTooltip> to specify which IPs should be used by Cloudflare in DNS responses when a record is <GlossaryTooltip term="proxy status" link="/dns/proxy-status/">proxied</GlossaryTooltip>.
 
 You can choose between two different scopes:
 

src/content/docs/cache/concepts/default-cache-behavior.mdx

@@ -59,7 +59,7 @@ Cloudflare’s CDN provides several cache customization options:
 
 <FeatureTable id="network.max_upload_size" />
 
-If you require a larger upload, group requests smaller than the upload thresholds or upload the full resource through an [unproxied (grey-clouded) DNS record](/dns/manage-dns-records/reference/proxied-dns-records/).
+If you require a larger upload, group requests smaller than the upload thresholds or upload the full resource through an [unproxied (grey-clouded) DNS record](/dns/proxy-status/).
 
 ### Cacheable size limits
 

src/content/docs/cache/get-started.mdx

@@ -22,7 +22,7 @@ Cloudflare caches static content based on the following factors:
 * Origin headers that indicate <GlossaryTooltip term="dynamic content">dynamic content</GlossaryTooltip>
 * Cache rules that bypass cache on cookie
 
-Cloudflare only caches resources within the Cloudflare data center that serve the request. Cloudflare does not cache off-site or third-party resources, such as Facebook or Flickr, or content hosted on [unproxied (grey-clouded)](/dns/manage-dns-records/reference/proxied-dns-records/) DNS records.
+Cloudflare only caches resources within the Cloudflare data center that serve the request. Cloudflare does not cache off-site or third-party resources, such as Facebook or Flickr, or content hosted on [unproxied (grey-clouded)](/dns/proxy-status/) DNS records.
 
 ## Learn the basics
 

src/content/docs/cache/how-to/cache-rules/index.mdx

@@ -11,7 +11,7 @@ Cache Rules can be created in the [dashboard](/cache/how-to/cache-rules/create-d
 
 :::note[Notes]
 
-Cache Rules require that you [proxy the DNS records](/dns/manage-dns-records/reference/proxied-dns-records/) of your domain (or subdomain) through Cloudflare.
+Cache Rules require that you [proxy the DNS records](/dns/proxy-status/) of your domain (or subdomain) through Cloudflare.
 
 Rules can be versioned. Refer to the [Version Management](/version-management/) documentation for more information.
 

src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx

@@ -11,7 +11,7 @@ Cache-tag purging makes multi-file purging easier because you can instantly bulk
 ## General workflow for cache-tags
 
 1. Add tags to the `Cache-Tag` HTTP response header from your origin web server for your web content, such as pages, static assets, etc.
-2. [Ensure your web traffic is proxied](/dns/manage-dns-records/reference/proxied-dns-records/) through Cloudflare.
+2. [Ensure your web traffic is proxied](/dns/proxy-status/) through Cloudflare.
 3. Cloudflare associates the tags in the `Cache-Tag` HTTP header with the content being cached.
 4. Use specific cache-tags to instantly purge your Cloudflare CDN cache of all content containing that cache-tag from your dashboard or [using our API](/api/resources/cache/methods/purge/).
 5. Cloudflare forces a [cache MISS](/cache/concepts/cache-responses/#miss) on content with the purged cache-tag.

src/content/docs/calls/turn/custom-domains.mdx

@@ -32,7 +32,7 @@ Any DNS provider, including Cloudflare DNS can be used to set up a CNAME for cus
 :::note
 
 
-If Cloudflare's authoritative DNS service is used, the record must be set to [DNS-only or "grey cloud" mode](/dns/manage-dns-records/reference/proxied-dns-records/#dns-only-records).\`
+If Cloudflare's authoritative DNS service is used, the record must be set to [DNS-only or "grey cloud" mode](/dns/proxy-status/#dns-only-records).\`
 
 
 :::

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works.mdx

@@ -20,7 +20,7 @@ To give the SaaS provider permission to route traffic through their zone, any cu
 
 ## With O2O
 
-If you have your own Cloudflare zone (`example.com`) and your zone contains a [proxied DNS record](/dns/manage-dns-records/reference/proxied-dns-records/) matching the custom hostname (`mystore.example.com`) with a **CNAME** target defined by the SaaS Provider, then O2O will be enabled.
+If you have your own Cloudflare zone (`example.com`) and your zone contains a [proxied DNS record](/dns/proxy-status/) matching the custom hostname (`mystore.example.com`) with a **CNAME** target defined by the SaaS Provider, then O2O will be enabled.
 
 <Example>