In a Cloudflare partial (CNAME) setup, what does the existing authoritative DNS provider publish, and which plans allow it?
answer
- the other provider stays authoritative
- Business or Enterprise only
- a verification TXT record
- hostname CNAMEs to cdn.cloudflare.net
basics
~10 sThe existing provider stays authoritative and publishes a cloudflare-verify TXT record plus, for every hostname to proxy, a CNAME to that hostname under cdn.cloudflare.net. A partial setup needs a Business or Enterprise plan.
solid answer
~40 sA partial setup keeps the current DNS provider authoritative; Cloudflare only proxies the hostnames pointed at it. You add the zone on a **Business** or **Enterprise** plan and select **Convert to CNAME DNS Setup**, or create it through the API with `type: partial`. The authoritative provider then publishes the **Verification TXT Record** (`cloudflare-verify.example.com`), which activates the zone and must stay for as long as the setup does. For each hostname to proxy it publishes a CNAME to `<hostname>.cdn.cloudflare.net` in place of that hostname's old A, AAAA or CNAME records, while the Cloudflare zone holds the A, AAAA or CNAME record that tells the proxy where the origin is. The apex can be proxied only if the provider can flatten a CNAME there, and domains on Cloudflare Registrar cannot use this setup.
go deeper
Remember that a partial setup leaves the other provider authoritative and sends chosen hostnames to Cloudflare through CNAMEs to cdn.cloudflare.net.
Walk through the verification TXT record, the per-hostname CNAMEs, the origin record kept in Cloudflare, and the Business or Enterprise plan requirement.
Name the operational traps: the apex without provider flattening, per-hostname certificate timing, a deleted verification record and same-zone CNAME targets resolving inside Cloudflare.
Frame partial as a deliberate split of ownership between two providers, and say what it costs in protection and process compared with a full setup.
## What stays where A **partial setup**, which Cloudflare also calls a **CNAME setup**, splits a domain between two parties. The existing DNS provider stays **authoritative**: resolvers still ask its nameservers, and the registrar's delegation is untouched. Cloudflare becomes a **reverse proxy for chosen hostnames only**. A hostname reaches the proxy because the authoritative provider answers for it with a CNAME into Cloudflare, and Cloudflare in turn needs its own record to know where that hostname's origin lives. It suits a client who must keep its DNS where it is, because of policy, an internal tool built on the provider's API, or a contract, but still wants Cloudflare's proxy in front of a few hostnames. ## Setting it up 1. **Choose the plan.** A partial setup is available on **Business** and **Enterprise** only; on Free or Pro the conversion option is not shown. 2. **Add the zone without changing nameservers.** Ignore the onboarding prompt to change them. In the dashboard, select **Convert to CNAME DNS Setup** on the **Overview** page; through the API, create the zone with `"type": "partial"`. 3. **Publish the verification record** at the authoritative provider: a TXT record named `cloudflare-verify` with the value Cloudflare shows. Verification can take up to a few hours, and the record must stay for as long as the zone uses this setup. If the provider appends the domain to record names automatically, enter only `cloudflare-verify`, or the name comes out doubled. 4. **Point each hostname at Cloudflare.** At the authoritative provider, create `www.example.com CNAME www.example.com.cdn.cloudflare.net` and remove that hostname's other A, AAAA or CNAME records. 5. **Keep the origin record in Cloudflare.** The Cloudflare zone holds the A, AAAA or CNAME record for each proxied hostname, and that record is what the proxy uses to find the origin. Until the TXT record is verified the zone sits in **Pending Nameserver Update**, even though no nameserver changes; that status name covers both setups. ## The records on each side | Where | Records | Purpose | | --- | --- | --- | | Authoritative provider | `cloudflare-verify` TXT | Proves control and keeps the zone active | | Authoritative provider | `<hostname>` CNAME `<hostname>.cdn.cloudflare.net` | Sends visitors to Cloudflare's proxy | | Authoritative provider | Everything else (MX, TXT, unproxied names) | Served as before | | Cloudflare zone | A, AAAA or CNAME per proxied hostname | Tells the proxy where the origin is | ## Limits that shape the choice - **The apex is awkward.** A CNAME is not allowed at the zone apex, so `example.com` can be proxied only if the authoritative provider supports CNAME flattening. Otherwise redirect the apex to a proxied subdomain, or use static or BYOIP addresses from Cloudflare. - **DNS-layer DDoS protection is missing.** Protection against attacks on DNS infrastructure applies only to full setups, because a partial zone does not use Cloudflare's authoritative nameservers. - **No Cloudflare Registrar.** Domains registered through Cloudflare Registrar must stay on a full setup. - **Certificates come per hostname.** With Universal SSL, a hostname gets its edge certificate only once its record is proxied, so plan certificate validation ahead for a hostname that cannot take downtime. - **Moved status.** A partial zone moves to **Moved** when repeated checks find no `SOA` record returned for it. - **Ownership.** If two accounts add the same partial zone, the last one to complete setup takes it; Enterprise zone holds prevent that. ## A resolution trap inside the partial zone Cloudflare resolves CNAMEs inside a partial zone itself. If `sub1` is a CNAME to `sub2` and the Cloudflare zone also holds an A record for `sub2`, proxied requests for `sub1` go to that A record's address and never consult the authoritative provider's record for `sub2`. Cloudflare warns when you create such a pair, and the safe pattern is to keep a CNAME's target out of the partial zone unless both copies agree.
- How do you proxy the apex on a partial setup when the authoritative provider cannot flatten a CNAME at the apex?You cannot point the apex at `cdn.cloudflare.net` with a plain CNAME. Redirect apex traffic to a proxied subdomain such as `www`, at the web server or the provider, or use static IPs or BYOIP addresses from Cloudflare so the provider can publish A and AAAA records for the apex.
- On a partial setup, how does a request for www.example.com find the origin?The authoritative provider answers with a CNAME to `www.example.com.cdn.cloudflare.net`, which resolves to Cloudflare's addresses. The proxy then looks up `www.example.com` in the Cloudflare zone and sends the request to the origin named by that A, AAAA or CNAME record, never to whatever the provider published before.
- A partial setup only works after the registrar points at Cloudflare's nameservers.
- The cloudflare-verify record can be deleted once the zone shows Active.
- A partial setup is a cheaper option available on the Free plan.
- The authoritative provider keeps an A record with the origin IP for a proxied hostname.
- On a partial setup Cloudflare protects the zone's nameservers from DDoS attacks.