skip to content

As the lead onboarding a client that wants to keep its current DNS provider, how do you decide between a Cloudflare full setup and a partial setup?

level: principalimportance: should knowfreq 25%

answer

  1. who answers for the zone
  2. plan floor and Registrar
  3. the apex and DNS-layer DDoS
  4. two places to change records
  5. partial can convert to full later

basics

~20 s

Choose full when Cloudflare can be authoritative: any plan, DNS-layer DDoS protection, Cloudflare DNSSEC, one place for records. Choose partial only when the provider must stay authoritative and the client accepts a Business plan, per-hostname CNAMEs and a provider-dependent apex.

solid answer

~50 s

I start by testing the requirement: is keeping the provider a hard constraint, such as a contract, a compliance rule or tooling built on its API, or habit? If it is habit, a **full setup** is simpler: it runs on every plan, gives DNS-layer DDoS protection, one-click DNSSEC and Cloudflare Registrar, and keeps records in one place. If the constraint is real, a **partial setup** works on **Business** or **Enterprise**: the provider stays authoritative and each proxied hostname gets a CNAME to `cdn.cloudflare.net`. The team then carries two places to change records, a per-hostname certificate step, an apex that works only if the provider flattens CNAMEs, and DNSSEC left with the provider. On Enterprise, zone transfers can make Cloudflare a secondary or primary beside the provider. I write down who owns each record and when we would convert to full.

go deeper

for a junior

Know the two setups by who is authoritative: Cloudflare in a full setup, the existing provider in a partial one.

for a middle

Compare the setups on plans, activation, apex handling, DNSSEC and DNS-layer DDoS protection.

for a senior

Name the failures a partial setup invites, such as records drifting between providers or a deleted verification record, and how to prevent them.

for a principal

Test whether keeping the provider is a real constraint, choose full, partial or zone transfers on that basis, and record the owners and the trigger for converting.

## The question behind the choice Cloudflare offers several ways for a domain to use it. A **full setup** makes Cloudflare the authoritative DNS provider. A **partial (CNAME) setup** leaves another provider authoritative and sends chosen hostnames to Cloudflare's proxy. On **Enterprise**, **zone transfers** let Cloudflare serve the zone as a primary or secondary beside another provider. The lead's real decision is who answers for the zone, because almost every other difference follows from that. So the first step is to test the client's reason for keeping its provider: - **Hard constraints**: a contract, a regulator's or group policy's requirement on where DNS lives, internal automation built on the provider's API, or another team owning the zone. - **Soft reasons**: habit, fear of the migration, records nobody has documented. These argue for a careful full migration, not for a permanent split. ## What each setup gives and costs | | Full setup | Partial (CNAME) setup | | --- | --- | --- | | Plans | Free, Pro, Business, Enterprise | Business and Enterprise | | Who is authoritative | Cloudflare | The existing provider | | Activation | Nameserver change at the registrar | `cloudflare-verify` TXT record at the provider | | Apex | CNAME at the apex flattened by Cloudflare | Only if the provider flattens CNAMEs, or a redirect, or static or BYOIP addresses | | DDoS protection for DNS infrastructure | Yes | No, Cloudflare's nameservers are not used | | DNSSEC | Signed by Cloudflare, one click on Registrar | Stays with the authoritative provider | | Cloudflare Registrar | Supported | Not supported | | Adding a proxied hostname | One record in Cloudflare | A record in Cloudflare plus a CNAME at the provider | ## The costs a partial setup leaves with the team - **Two sources of truth.** Every proxied hostname needs a record in the Cloudflare zone and a CNAME at the provider. Someone has to own both, and a hostname changed in one place only quietly bypasses the proxy or sends it to the wrong origin. - **A record that must never be deleted.** The `cloudflare-verify` TXT record keeps the zone active; a tidy-up at the provider can take the whole setup down. - **Certificate timing per hostname.** With Universal SSL, each hostname gets its certificate only once proxied, so a new hostname needs a validation plan before it carries traffic. - **Weaker protection at the DNS layer.** Attacks on DNS servers are the provider's problem, and so is DNSSEC. - **Plan cost.** The Business plan becomes the floor for every zone that needs this arrangement. ## Options beyond full and partial - **Cloudflare as secondary** (zone transfers, Enterprise only): the existing provider remains primary and transfers the zone to Cloudflare with AXFR or IXFR, so both answer authoritatively and the client keeps its tooling. This fits "keep the provider" better than a partial setup when the aim is resilience. - **Cloudflare as primary** with the other provider as secondary, reversing the roles, also through Enterprise zone transfers. - **Multi-provider DNS** on a full setup lets the registrar list other providers' nameservers beside Cloudflare's; combined with DNSSEC, it needs **multi-signer DNSSEC**. ## Planning the exit from partial A partial zone can later become full without re-onboarding: 1. **Have edge certificates ready**, ideally an advanced or custom certificate that is already active. 2. **Turn off DNSSEC at the authoritative provider** at least 24 hours before converting. 3. **Select Convert to Primary DNS** on **DNS Settings**, and import the full record set, usually unproxied at first. 4. **Change the nameservers** at the registrar; if Universal SSL is what covers the site, do it within 72 hours of the conversion. 5. **Enable DNSSEC** on Cloudflare and add its DS. Previously proxied hostnames keep being proxied throughout. ## A decision record worth writing - The constraint that justified partial, and who confirmed it. - Who owns the Cloudflare zone and who owns the provider zone, and how a new hostname request reaches both. - The trigger for converting to full, such as the contract ending, the tooling being replaced, or an incident caused by the split. - How DNSSEC and DNS-layer DDoS protection are covered in the meantime.

  • The client's real need is resilience if one DNS provider fails. Is a partial setup the right answer?
    No. A partial setup still has a single authoritative provider, the existing one, so a provider outage takes down every hostname, proxied or not. Resilience needs two authoritative providers: on Enterprise, zone transfers with Cloudflare as secondary or primary, or multi-provider DNS on a full setup, with multi-signer DNSSEC if the zone is signed.
  • What would make you move a partial-setup client to a full setup?
    The constraint going away, or the split causing incidents: a hostname changed at the provider but not in Cloudflare, a deleted verification record, or an apex that cannot be proxied. The conversion is planned: certificates ready, DNSSEC off at the provider 24 hours before, Convert to Primary DNS, records imported, then the nameserver change and Cloudflare DNSSEC.

  • A partial setup is the cautious default for any client new to Cloudflare.
  • Partial and full setups give the same protection, since both proxy the hostnames.
  • A partial setup keeps the domain up if the existing DNS provider fails.
  • Moving from partial to full means deleting the zone and onboarding it again.
  • Any Cloudflare plan can keep its DNS elsewhere with a partial setup.