diff --git a/src/content/docs/dns/zone-setups/partial-setup/index.mdx b/src/content/docs/dns/zone-setups/partial-setup/index.mdx
index 2b2d0595627560d..1fef8eec0c18489 100644
--- a/src/content/docs/dns/zone-setups/partial-setup/index.mdx
+++ b/src/content/docs/dns/zone-setups/partial-setup/index.mdx
@@ -10,13 +10,14 @@ import { FeatureTable, Render } from "~/components"
-Once you are on a partial setup, the actual resolution of your records to Cloudflare depends on `CNAME` records [added at your authoritative DNS provider](/dns/zone-setups/partial-setup/setup/#3-add-dns-records). Check your authoritative DNS provider to know which records are pointing to `{your-hostname}.cdn.cloudflare.net`.
+Once you are on a partial setup, the actual resolution of your records to Cloudflare depends on CNAME records [added at your authoritative DNS provider](/dns/zone-setups/partial-setup/setup/#3-add-dns-records). Check your authoritative DNS provider to know which records are pointing to `{your-hostname}.cdn.cloudflare.net`.
## How to
* [Set up a partial domain](/dns/zone-setups/partial-setup/setup/)
* [Convert a partial setup to a full setup](/dns/zone-setups/conversions/convert-partial-to-full/)
* [Convert a partial setup to a secondary setup](/dns/zone-setups/conversions/convert-partial-to-secondary/)
+* [Create DNS records of other types](/dns/zone-setups/partial-setup/setup/#other-record-types)
## Availability
@@ -30,7 +31,7 @@ With a partial zone, Cloudflare resolves [DNS records differently](/dns/zone-set
### CNAME flattening
-A partial (`CNAME`) setup requires the proxied hostname to be pointed to Cloudflare via a `CNAME` record. Since [`CNAME` records are not allowed on the zone apex](https://datatracker.ietf.org/doc/html/rfc1912#section-2.4) (`example.com`), you can only proxy your zone apex to Cloudflare if your authoritative DNS provider supports [`CNAME` Flattening](https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/).
+A partial (CNAME) setup requires the proxied hostname to be pointed to Cloudflare via a CNAME record. Since [CNAME records are not allowed on the zone apex](https://datatracker.ietf.org/doc/html/rfc1912#section-2.4) (`example.com`), you can only proxy your zone apex to Cloudflare if your authoritative DNS provider supports [CNAME Flattening](https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/).
If your authoritative DNS provider does not support CNAME Flattening, redirect its traffic — for example, with an `.htaccess` file — to a subdomain proxied to Cloudflare. Alternatively, you can use [static IPs or BYOIPs](/fundamentals/concepts/cloudflare-ip-addresses/#customize-cloudflare-ip-addresses).
diff --git a/src/content/docs/dns/zone-setups/partial-setup/setup.mdx b/src/content/docs/dns/zone-setups/partial-setup/setup.mdx
index b282cfcd0d450b5..886ab2ad0b41f71 100644
--- a/src/content/docs/dns/zone-setups/partial-setup/setup.mdx
+++ b/src/content/docs/dns/zone-setups/partial-setup/setup.mdx
@@ -38,7 +38,7 @@ A partial setup is only available to customers on a Business or Enterprise plan.
1. On the **Overview** page, select **Convert to CNAME DNS Setup**.
2. Select **Convert** to confirm.
3. Save the information from the **Verification TXT Record**. If you lose the information, you can also access it by going to **DNS** > **Records** > **Verification TXT Record**.
-4. Make sure that you have all the DNS records for subdomains that you want to proxy through Cloudflare.
+4. Make sure that you have all the DNS records (A, AAAA, or CNAME) for subdomains that you want to proxy through Cloudflare.
## 2. Verify ownership for your domain
@@ -81,4 +81,10 @@ If your organization has multiple Cloudflare accounts, also consider using zone
2. Remove any previously existing `A`, `AAAA`, or `CNAME` records referencing the hostnames you want to proxy through Cloudflare. For these hostnames, leave only the records pointing to `{your-hostname}.cdn.cloudflare.net`.
2. Repeat this process for each subdomain that should be proxied to Cloudflare.
-
\ No newline at end of file
+
+
+---
+
+## Other record types
+
+If you are preparing a conversion from partial to full setup, or if you have a more specific use case, you can use the [Create DNS Record](/api/operations/dns-records-for-a-zone-create-dns-record) API endpoint to create DNS records of any supported type.
\ No newline at end of file
diff --git a/src/content/partials/dns/partial-setup-definition.mdx b/src/content/partials/dns/partial-setup-definition.mdx
index 6d3e229b0de6375..d473a7309a3e660 100644
--- a/src/content/partials/dns/partial-setup-definition.mdx
+++ b/src/content/partials/dns/partial-setup-definition.mdx
@@ -5,6 +5,6 @@
import { GlossaryTooltip } from "~/components"
-A partial (`CNAME`) setup allows you to use [Cloudflare's reverse proxy](/fundamentals/concepts/how-cloudflare-works/) while maintaining your primary and authoritative DNS provider.
+A partial (CNAME) setup allows you to use [Cloudflare's reverse proxy](/fundamentals/concepts/how-cloudflare-works/) while maintaining your primary and authoritative DNS provider.
-Use this option to proxy only individual subdomains through Cloudflare's global network when you cannot change your authoritative DNS provider.
+Use this option to proxy only individual subdomains through Cloudflare when you cannot change your authoritative DNS provider. You will be able to create A, AAAA, and CNAME records, which are the DNS record types that can be [proxied](/dns/manage-dns-records/reference/proxied-dns-records/).