Summary

  • Cloudflare Registrar charges registration and renewal at cost, without a markup, while requiring Cloudflare nameservers. Using another authoritative DNS provider requires moving the domain to another registrar.
  • Switching off the web proxy, delegating a subdomain and branding nameservers offer narrower choices. None, by itself, replaces the authoritative DNS operator for the parent domain.

The renewal invoice contains a pleasing omission: no registrar markup. The next DNS change contains a less pleasing addition: a registrar transfer. Cloudflare has made one part of the purchase admirably easy to price. Buyers still have to read how the parts fit together.

Cloudflare Registrar’s product description says registration and renewal are charged at the cost imposed by the registry and ICANN, without a markup. The domain is paid for. The intermediary simply removes its own price increment.

The Registrar FAQ supplies the attachment. Domains registered with the service must use Cloudflare nameservers. To use another provider’s nameservers, the customer must move the domain to another registrar. A decision about who answers DNS queries becomes a decision about who handles the registration as well.

The cheap line item has a second job

Authoritative DNS publishes the reference answers for a domain. A registrar handles its registration and renewal relationship. These are separate functions, even when one company puts them behind the same account.

There is a straightforward case for combining them. A team already committed to Cloudflare DNS can reduce the number of accounts and handovers it manages while avoiding a registration markup. Administrative convenience is real value, especially when a small team has more services than spare afternoons.

The combination becomes more interesting when the team changes its mind. Suppose it wants a different authoritative DNS operator while keeping its website, email service and domain name. Registrar turns that single substitution into a coordinated change across two functions. The engineer who edits DNS records may now need the person who controls the domain account and can authorise its transfer.

Actual customer transfer times and incremental labour bills were not available in the materials examined; those records would put a price on the extra work. The documented condition already establishes the extra step. Replacing this DNS provider requires replacing the registrar.

Procurement can therefore report a genuine saving while operations later inherits a genuine task. Neither department needs to have made an arithmetic mistake. They have simply counted different portions of the same purchase.

A grey cloud is not a new DNS company

Cloudflare offers a DNS-only setting for eligible records. Its proxy-status documentation explains the ordinary address-record case: a DNS-only answer can return the origin server’s address, allowing web requests to travel directly to that origin.

That changes the route of HTTP or HTTPS traffic. It does not appoint a different company to answer authoritative DNS queries. Cloudflare can leave the web traffic path while remaining the DNS operator.

Mixed record sets and CNAME chains have additional proxy behaviour, so an individual setting is not a complete description of every request’s route either. For the purchasing question, the essential distinction is simpler: choosing whether to use a web proxy and choosing who operates authoritative DNS are different freedoms. Registrar’s nameserver requirement concerns the latter.

Custom nameservers can create a second misunderstanding. The FAQ describes the Business and Enterprise option as Cloudflare nameservers with custom branding. The customer can change the sign on the door. The company on duty stays the same. A familiar corporate name in a nameserver address is a poor substitute for knowing who operates the service.

A subdomain can take the side exit

The FAQ allows a subdomain to be delegated to another provider. That can be enough for a project or department needing separate DNS administration. A careful assessment should give the exception its proper weight: not every local requirement calls for a wholesale transfer.

But delegating part of the namespace does not replace the authoritative DNS provider for the parent domain. If the operating requirement is to change that parent service, Registrar’s transfer condition remains.

“Supports external DNS” is consequently an unfinished answer in a procurement questionnaire. External DNS for what? A delegated subdomain, custom-branded server names and replacement of the parent domain’s DNS operator describe different arrangements. Combining them into one cheerful tick saves space on the form and spends time in the eventual change meeting.

Precision also prevents needless work. A team that only needs a delegated branch should not be pushed into transferring the whole registration. A team that needs another parent-domain operator should not be offered the branch as though it solves the same problem.

Five days belongs to an approval, not an entire move

Cloudflare’s transfer-out instructions describe an available route. The customer unlocks the domain and obtains an authorisation code; the new registrar submits the transfer request through the registry, and Cloudflare receives it for approval. The specific domain’s eligibility and lock status matter when planning the operation.

After receipt, the customer can approve manually. Without manual approval, the documentation says Cloudflare automatically approves on the fifth day after receiving the request. That number describes an approval stage. It does not absorb preparation of the destination DNS, any wait for transfer eligibility, or verification of the eventual DNS change.

Calling it a five-day migration would turn one desk’s processing timetable into a promise for the whole removal van. Operations needs to coordinate the registration transfer with continuing DNS service, while measuring the events separately.

The exit is real. It simply goes through the registrar as well as the DNS relationship. That is the product’s economic detail: an easily compared markup disappears, while a dependency between functions remains. Buyers can value the convenience and still count the work needed to separate it later.

An at-cost domain is a clear offer. The conditions for choosing its next DNS operator deserve equally clear space beside the price.