DoDomain

Add a CNAME, A or TXT record at Cloudflare

Where DNS records live at Cloudflare, what goes in the host field for a subdomain and for the root domain, and how to check the record is live — the same steps DoDomain's connect flow shows Cloudflare users.

These are the steps DoDomain's hosted connect flow shows a customer whose domain is managed at Cloudflare, in Cloudflare's own vocabulary. A product using DoDomain never writes them: the connect flow detects the provider, shows these steps beside the exact records to create, and verifies each record against the zone's authoritative nameservers. They are published here for your own support articles, and for anyone who wants to see the steps before they start.

Where the records live

Cloudflare's DNS page for a domain is https://dash.cloudflare.com/?to=/:account/<your-domain>/dns — replace <your-domain> with the domain you are editing. (The hosted connect flow opens it for you with the right domain filled in.)

Step by step

  1. Open the Cloudflare dashboard and pick your domain.
  2. Go to DNS → Records → Add record.
  3. Add each record below. For CNAME/A on a website, set Proxy status to DNS only if verification stalls.
  4. Save, then come back and click Verify.

What goes in the host field

Enter the subdomain only (e.g. www); Cloudflare appends the domain. For a record on the domain itself, enter @.

Whatever the panel calls the field — Name, Host, Hostname — DoDomain's connect flow shows the value to paste into it already in this provider's format, and shows the fully-qualified name it will verify next to it.

Worth knowing

  • Proxied A/CNAME records won't show their real value on public DNS — that's expected.

Check the record is live

A saved record is not yet a live record. DoDomain verifies against the zone's authoritative nameservers, which answer as soon as the provider publishes the change; public resolvers can lag behind for as long as the old answer's TTL. The free DNS lookup shows both answers side by side for any name, and the provider detector tells you which provider serves a domain and whether a one-click path exists for it.

If you are the product asking for this record

You do not have to send customers here. Mint a connect session and the hosted flow shows these steps to your Cloudflare customers on its own, then verifies and keeps monitoring the records — see the connect flow and the framework guides for Next.js, Rails, Laravel and Django. A customer who wants their bare domain rather than a subdomain is the apex question, which no provider panel solves on its own.

Vocabulary checked against Cloudflare's own help page on 2026-09-05: https://developers.cloudflare.com/dns/manage-dns-records/reference/dns-record-types/.

On this page