Cloudflare Registrar or a registrar with custom DNS?

Quick answer: Choose Cloudflare Registrar when you are comfortable keeping Cloudflare as the domain’s authoritative DNS provider as well as its registrar. Keep registration at a registrar that permits third-party nameservers when your host or future operating plan needs a different authoritative DNS provider for the whole domain. You can still use Cloudflare DNS without transferring registration: set Cloudflare’s nameservers at the current registrar. Sources: Cloudflare Registrar FAQ, Cloudflare nameserver setup.

Important constraint: Cloudflare Registrar requires Cloudflare-operated nameservers for its registered domains. A host’s request that you point a few A, AAAA, CNAME or MX records to its service is usually compatible with that arrangement; a demand that you replace the domain’s authoritative nameservers with the host’s is a different requirement. Confirm which instruction the host actually gives before transferring the registration. Sources: Cloudflare Registrar FAQ, Namecheap hosting connection guide.

Namecheap is one documented registrar with CustomDNS for third-party nameservers; its controls do not represent every retail registrar. Use the roles below to identify which account must hold each service.

Separate registration, DNS, web and mail

The registrar holds the registration and manages renewal and transfer. The authoritative DNS provider publishes the records that make hostnames resolve. The web host runs the site or app. The mail provider receives and sends mail for addresses at the domain. One company can provide more than one role, but the roles remain distinct. Moving registration does not itself relocate the website or inbox, and adopting a different DNS provider does not by itself transfer registration.

That map prevents a common misunderstanding: “My site is moving, so the registration must move too.” A new web host may only need DNS records changed. Conversely, a registrar transfer may leave hosting untouched while requiring a DNS change because the gaining registrar has a nameserver rule. Cloudflare’s Registrar FAQ documents that constraint for its product. Namecheap’s hosting connection guide distinguishes a nameserver-based hosting setup from pointing records to a server. Ask the prospective host which path it supports for your exact product.

When reading setup instructions, look for the object being changed. A request to set www to a CNAME or the apex to an IP address changes records inside the existing zone. A request to enter two new nameserver hostnames at the registrar changes who answers authoritatively for the zone. Those actions have different ownership and migration consequences, even if both are described as “pointing the domain.” If the host provides both methods, ask which one supports the features you need and who will maintain mail and verification records after the change.

Compare the DNS constraint, not a generic feature score

The Namecheap column describes one provider’s published control, not a universal retail-registry feature. Other registrars may have different DNS rules, interfaces and account permissions. Also, “separate accounts” is not automatically safer or easier: it gives you a clearer split between renewal and zone management but creates two access and billing dependencies. Document who can make each change and who is alerted if either account has a problem.

Cloudflare allows subdomain DNS delegation while requiring Cloudflare nameservers for the registered domain. That can solve a narrower requirement—say, giving an app team authority over app.example.com—without handing the entire domain’s nameservers to another DNS provider. It does not satisfy a vendor that explicitly requires the apex domain itself to use its nameservers. Confirm whether the requirement is for a delegated subdomain, an individual DNS record, or the whole zone.

Three scenarios that lead to different decisions

1. You already use Cloudflare DNS and expect to keep it. The website is hosted elsewhere, mail is hosted by a separate provider, and the team is comfortable maintaining those records in Cloudflare. Cloudflare Registrar can consolidate registration and DNS without moving the website or inbox. Keep the web and mail contracts and record inventory separate. You do not need to transfer registration merely to use Cloudflare DNS if the current registrar permits that delegation. Consolidation also places renewal and zone administration within one service boundary: name who can renew, edit records and recover access if that account is lost. If finance owns renewals while engineering owns DNS, record whether one account’s permission model serves both jobs or separate accounts remain preferable.

2. A host requires its own authoritative nameservers for the full domain. First check whether it truly needs delegation or can provide record values for the existing zone. If it must control the apex nameservers, Cloudflare Registrar’s rule conflicts with that requirement. A registrar that supports third-party nameservers, such as Namecheap’s documented CustomDNS option, is a more direct fit. If the domain is already at Cloudflare Registrar, changing to another apex DNS provider entails a registrar move too. A nameserver switch does not automatically copy the existing zone: Namecheap’s instructions tell users to preserve needed records. Inventory web hostnames, mail routing, sender authentication, verification entries and delegations; create and verify them at the new provider before changing authority. Assign people to check both web and mail after the handoff.

3. Only one subdomain needs independent DNS. Suppose the main site and mail stay in Cloudflare DNS, while an application team needs to manage app.example.com at another DNS provider. Cloudflare’s subdomain-delegation option may preserve the main-domain arrangement. Define which team owns the parent delegation and which owns the child zone. Check a test record through the delegated path, then verify the application and any subdomain-specific mail or verification records. A subdomain solution works only if the dependent vendor’s instructions allow it.

Prepare the DNS handoff by service

If the registrar or authoritative DNS provider will change, make a record inventory before touching the delegation. Put the current value, intended new value, service owner and verification result on one sheet. A record that looks obsolete may still support a login, mail sender or external verification; have its owner decide before omitting it. Date the inventory so a later operator knows which configuration it describes.

Record both the old and intended nameserver values, and which account can change the registrar’s delegation or edit the new zone. If a check fails, the owner needs the old values and access to the relevant accounts, not merely a message that the transfer completed. Keep the change record with the next renewal owner so the new arrangement remains understandable after the migration team moves on.

Check three facts before a transfer

Get the host’s exact DNS instruction, including whether it needs record values or its own authoritative nameservers. Identify the DNS provider your team intends to operate, with owners for record changes and account recovery. Then confirm whether the chosen registrar must allow a future apex-nameserver change. These three answers determine whether Cloudflare Registrar, Cloudflare DNS with registration elsewhere, or a registrar with third-party delegation fits the arrangement.

Only then compare renewal terms and transfer timing. Keep the verified zone inventory beside the registrar decision: a transfer notice says nothing about whether the new web and mail records work. The domains hub covers renewal and transfer questions separately.