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

Author: RebeccaTamachiro

src/content/docs/dns/proxy-status/index.mdx

@@ -3,13 +3,97 @@ pcx_content_type: navigation
 title: Proxy status
 sidebar:
   order: 7
+  label: Overview
   group:
-    hideIndex: true
-    label: Proxying
+    label: Proxy status
 ---
 
-Refer to the following sections to learn more about proxying with Cloudflare DNS.
+import { Render, Example, Details, GlossaryTooltip } from "~/components";
 
-import { DirectoryListing } from "~/components";
+While your [DNS records](/dns/manage-dns-records/) are used to make your website or application available to visitors and other web services, the **Proxy status** of a DNS record is used to define how Cloudflare treats incoming traffic to that record.
 
-<DirectoryListing />
+The records you can proxy through Cloudflare are [IP resolution records](/dns/manage-dns-records/reference/dns-record-types/#ip-address-resolution) — meaning A, AAAA, or CNAME records.
+
+Cloudflare recommends setting to proxied all A, AAAA, and CNAME records that are used for serving web traffic. For example, CNAME records being used to verify your domain for a third-party service should not be proxied.
+
+:::note
+Proxying is on by default when you onboard a domain via the dashboard.
+:::
+
+### Benefits
+
+When you set a DNS record to **Proxied**, Cloudflare can:
+
+- Protect your origin server from [DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/).
+- [Optimize, cache, and protect](/fundamentals/setup/manage-domains/connect-your-domain/#domain-configurations) all requests to your application.
+- Apply your configurations for a variety of Cloudflare products.
+
+:::caution
+When you [add a domain](/fundamentals/setup/manage-domains/add-site/) to Cloudflare, Cloudflare protection will be in a [pending state](/dns/zone-setups/reference/domain-status/) until we can verify ownership. This could take up to 24 hours to complete. Refer to [Limitations](/dns/proxy-status/limitations/#pending-domains) for further guidance.
+:::
+
+### Example
+
+<Render file="proxy-status-dns-table" />
+
+This means that:
+
+- an HTTP/HTTPS request to the proxied record `blog.example.com` will be answered with a Cloudflare [anycast IP address](/fundamentals/concepts/cloudflare-ip-addresses/) instead of `192.0.2.1`, which allows the [benefits listed above](#benefits) to take place.
+- an HTTP/HTTPS request to the DNS-only record `shop.example.com` will be answered with the actual origin IP address, `192.0.2.2`. In addition to exposing your origin IP address and not benefitting from several features, Cloudflare cannot provide analytics on those requests.
+
+For further context, refer to [How Cloudflare works](/fundamentals/concepts/how-cloudflare-works/).
+
+---
+
+## Proxied records
+
+The sections below describe specific behaviors and expected outcomes when you have DNS records set to <GlossaryTooltip term="proxy status">proxied</GlossaryTooltip>. There may also be some [limitations](/dns/proxy-status/limitations/) in specific scenarios.
+
+### Predefined time to live
+
+
+By default, all proxied records have a time to live (TTL) of **Auto**, which is set to 300 seconds.
+
+Since only [IP resolution records](/dns/manage-dns-records/reference/dns-record-types/#ip-address-resolution) can be proxied, this setting ensures that queries to your domain name resolve fairly quickly. This setting also means that any changes to proxied A, AAAA, or CNAME records will take place within five minutes or less.
+
+:::note
+It may take longer than five minutes for you to actually experience record changes, as your local DNS cache may take longer to update.
+:::
+
+### Mix proxied and unproxied
+
+If you have multiple A or AAAA records on the same name and at least one of them is proxied, Cloudflare will treat all A or AAAA records on this name as being proxied.
+
+<Details header="Example">
+
+<Example>
+DNS management for **example.com**:
+
+| Type | Name    | Content      | Proxy status | TTL    |
+| ---- | ------- | ------------ | ------------ | ------ |
+| A    | `blog`  | `192.0.2.1`  | Proxied      | Auto   |
+| A    | `blog`  | `192.0.2.5`  | DNS only     | Auto   |
+
+In this example, all traffic intended for `blog.example.com` will be treated as if both records were **Proxied**.
+
+</Example>
+
+</Details>
+
+### Protocol optimization
+
+For proxied records, if your domain has [HTTP/2 or HTTP/3 enabled](/speed/optimization/protocol/), Cloudflare automatically generates corresponding [HTTPS Service (HTTPS) records](/dns/manage-dns-records/reference/dns-record-types/#svcb-and-https) on the fly. HTTPS records allow you to provide a client with information about how it should connect to a server upfront, without the need of an initial plaintext HTTP connection.
+
+:::note
+Both HTTP/2 and HTTP/3 configurations also require that you have an SSL/TLS certificate served by Cloudflare. This means that disabling [Universal SSL](/ssl/edge-certificates/universal-ssl/), for example, could impact this behavior.
+:::
+
+---
+
+## DNS-only records
+
+When an A, AAAA, or CNAME record is **DNS-only** — also known as being gray-clouded — DNS queries for these will resolve to the record's normal IP address, as described in the [example](#example).
+
+<Render file="mix-proxied-and-unproxied" product="dns" />
+
+In addition to potentially exposing your origin IP addresses to bad actors and [DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/), leaving your records as **DNS-only** means that Cloudflare cannot [optimize, cache, and protect](/fundamentals/concepts/how-cloudflare-works/) requests to your application or provide analytics on those requests.

src/content/docs/dns/proxy-status/limitations.mdx

@@ -1,14 +1,14 @@
 ---
 pcx_content_type: concept
-title: Proxied records limitations
+title: Proxying limitations
 sidebar:
   order: 2
   label: Limitations
 ---
 
 import { Render, GlossaryTooltip } from "~/components";
 
-This page describes expected limitations for DNS records <GlossaryTooltip term="proxy status">proxy status</GlossaryTooltip>.
+This page describes expected limitations when <GlossaryTooltip term="proxy status">proxying DNS records</GlossaryTooltip>. For further context, refer to [How Cloudflare works](/fundamentals/concepts/how-cloudflare-works/).
 
 ## Proxy eligibility