Easy Tech TutsHow to Add a Subdomain in Cloudflare Easily 2026
By Impran M NLast checked against official docs
A subdomain lets you carve out a separate section of your site, like shop.yoursite.com or blog.yoursite.com, without buying a new domain. In Cloudflare that just means adding one more row to the DNS records already sitting on your zone: no separate signup, no extra domain purchase, and it works the same on every plan including Free. This guide covers reaching the domain's Overview screen, opening DNS Records, and filling in the Add record form, whether you're pointing it directly at a server IP or aliasing it to another URL.
Before you start
- The parent domain already added to Cloudflare with its nameservers pointed there (the Overview page should show DNS Setup: Full)
- The IPv4 address or target hostname you want the subdomain to point to
01Open your domain's Overview in Cloudflare
After logging in, selecting a domain from your account drops you on its Overview screen, which shows unique visitors, total requests, and cache percentage over the last 24 hours, 7 days, or 30 days, alongside a DNS panel on the right confirming your DNS Setup is Full. The left sidebar is where every other section lives: Records, AI Crawl Control, Investigate, Analytics, DNS, Email, SSL/TLS, Security, and more, all scoped to whichever domain is currently selected at the top of the page.
02Expand DNS in the sidebar and open Records
Clicking DNS in the left sidebar expands it into three sub-items: Records, Analytics, and Settings. Records is what you want; it's the list of every A, AAAA, CNAME, MX, and TXT entry already configured for the domain. The same page surfaces an Active Subscriptions panel showing your current plan (Free, on a lot of small-site setups) and an API section with your Zone ID and Account ID, useful if you ever script DNS changes instead of using the dashboard.
03Click Add record and choose the type
On the DNS records page, the Add record button opens a modal titled "Add record," with a live description underneath that updates as you fill in the form, for example "[name] points to [IPv4 address] and has its traffic proxied through Cloudflare." The Type dropdown lists every record kind Cloudflare supports: A, AAAA, CAA, CERT, CNAME, DNSKEY, DS, HTTPS, LOC, MX, NAPTR, NS, OPENPGPKEY, and PTR among them. For a subdomain, the two you'll actually use are A, if you're pointing straight at a server's IPv4 address, or CNAME, if you're aliasing to another domain or a third-party platform's URL.
04Fill in the name and value, then set the proxy status
With Type set to A, the form settles into its final shape: a Name field with placeholder text reminding you to "use @ for root", meaning you only type the subdomain prefix like blog or shop, an IPv4 address field below it, a Proxy status toggle, and a TTL field set to Auto. The proxy toggle only appears for A, AAAA, and CNAME records; record types like MX or TXT skip it entirely because they never route through Cloudflare's edge.
Orange cloud (Proxied) sends traffic through Cloudflare first, which enables caching, DDoS protection, hides your origin server's real IP, and is also the only way Cloudflare can issue a free SSL certificate for that hostname. Gray cloud (DNS only) resolves straight to the IP with none of that, which is correct for records like a mail server, but means your own origin has to supply a valid certificate if the subdomain will be browsed over HTTPS. For a typical web-facing subdomain, leaving it proxied is the standard choice.
05Save and confirm the record resolves
Click Save on the modal and the new row appears in your DNS records table immediately. Cloudflare's own edge network picks up the change right away since it's authoritative for the zone; full propagation to every resolver worldwide can occasionally take a little longer, so give it a few minutes before assuming something's wrong if the subdomain doesn't resolve on the first try.
This is a plain DNS record inside your existing zone. Cloudflare also sells a separate, Enterprise-only "subdomain setup" that spins up an entirely independent zone for a subdomain when a different team needs to manage its own settings; almost nobody adding a single blog or shop subdomain needs that feature.
When it doesn't work
The subdomain doesn't resolve at all after saving
Why: Either the parent domain's nameservers haven't finished pointing to Cloudflare, or the record was saved on the wrong zone.
Fix: Check that the Overview page shows DNS Setup: Full, confirm the new row is listed under DNS > Records, then wait a few minutes for propagation before re-testing.
The subdomain throws a certificate warning even though it loads
Why: The record is set to DNS only. Cloudflare can issue an SSL certificate for a hostname only when its proxy status is Proxied; a DNS-only record depends entirely on the origin server's own certificate.
Fix: Switch the record to Proxied so Cloudflare covers it, or install a valid certificate on the origin server yourself if it needs to stay DNS only.
There's no Proxy status toggle on the record you're adding
Why: Proxying only applies to A, AAAA, and CNAME records. Every other type, MX and TXT included, is DNS only by design.
Fix: Nothing to fix; that's expected. If the record needs Cloudflare's edge features, it has to be an A, AAAA, or CNAME record.
Frequently asked questions
What's the difference between an A record and a CNAME for a subdomain?
An A record points your subdomain directly to a server's IPv4 address. A CNAME aliases it to another domain name instead, which is common when pointing at a third-party platform.
Should I proxy my new subdomain through Cloudflare?
Proxying (orange cloud) enables caching, DDoS protection, and a Cloudflare-issued SSL certificate. DNS-only mode (gray cloud) routes traffic straight to your origin with none of that, which is usually right for records like a mail server.
How long does it take for a new subdomain to start working?
Cloudflare's own edge network picks up the change almost immediately, though full global DNS propagation to every resolver can occasionally take longer.
Do I need an Enterprise plan to add a subdomain?
No. Adding a DNS record for a subdomain works on every Cloudflare plan, Free included. The paid, Enterprise-only "subdomain setup" feature is a different thing: a fully separate zone for cases where another team needs independent Cloudflare settings for that subdomain.
Can I add multiple subdomains to the same domain?
Yes. Add as many A or CNAME records as you need from the same DNS Records page, each with its own subdomain prefix in the Name field.
Sources and last check
Click path and screens come from a walkthrough recorded in July 2025. Record-type behavior, the proxy/SSL relationship, and the distinction between a plain DNS record and Cloudflare's Enterprise-only subdomain setup were re-checked against Cloudflare's official DNS documentation in September 2026, which is also where the certificate-warning troubleshooting entry came from.
About the author
Impran M N
I've been hooked on technology for as long as I can remember — especially the new tools and AI apps that seem to land every other week. Easy Tech Tuts is where I write up whatever I've just worked out: I do the task in the real product, record the screen, and turn it into the guide I wish I'd found first.
