Type | Name | IPv4 address | Proxy status |
---|---|---|---|
A | www | 192.0.2.1 | Proxied |
Most subdomains serve a specific purpose within the overall context of your website. For example, blog.example.com
might be your blog, support.example.com
could be your customer help portal, and store.example.com
would be your e-commerce site.
To create a new subdomain, you would first add the subdomain content at your host.
Then, you would create a corresponding A
, AAAA
, or CNAME
record for that subdomain (blog
, store
).
Type | Name | IPv4 address | Proxy status |
---|---|---|---|
A | www | 192.0.2.1 | Proxied |
For more guidance on redirecting a subdomain — either to your main domain or another location — refer to Set up subdomain redirects.
If your main domain is using Cloudflare’s Universal SSL certificate, that certificate also covers all first-level subdomains (blog.example.com
).
For deeper subdomains (dev.blog.example.com
), use a different type of certificate.
If you want to customize Cloudflare settings for individual subdomains, your approach will vary depending on your plan.
Enterprise customers can set up custom settings and access for a specific subdomain within Cloudflare with Subdomain support.
All other customers can set up subdomain-specific Configuration Rules or Page Rules to alter Cloudflare settings.
If you want a subdomain’s DNS settings managed totally outside of Cloudflare — meaning this subdomain can be managed by individuals without access to your Cloudflare account — refer to Delegating subdomains outside of Cloudflare.