Skip to main content
If your domain uses Cloudflare to manage its DNS — the system that tells browsers where to find your site — you should add Laravel Cloud’s DNS records in Cloudflare’s DNS dashboard. Laravel Cloud shows the exact records you need for your domain. This guide explains how to enter those records correctly in Cloudflare.

​
Before you start

Before adding any records, confirm that Cloudflare is the service responsible for your domain’s DNS. You can check this by running the following command in your terminal: 
dig NS example.com +short
If the output lists Cloudflare nameservers (e.g., anna.ns.cloudflare.com), you’re in the right place. If not, your DNS is managed elsewhere and you should add your records there instead.

​
Add the required DNS records

1

Open your domain in Cloudflare

In Cloudflare, select your website and open DNS.
2

Add the origin record(s) from Laravel Cloud

In Laravel Cloud, open your domain’s configuration and copy the origin record(s). These records tell Cloudflare where to send traffic for your domain.For the record name in Cloudflare:
  • Use @ for the root domain (for example, example.com).
  • Use www for www.example.com.
  • Use * for *.example.com (wildcards), if shown.
For proxy status (the orange / grey cloud icon in Cloudflare):
  • Origin records are typically safe to proxy (orange cloud) if you selected a Cloudflare proxy option in Laravel Cloud.
  • If you are unsure, start with the proxy status Laravel Cloud recommends in the UI.
3

Add the pre-verification TXT record (if shown)

If Laravel Cloud shows an ownership verification record like _cf-custom-hostname.example.com, add it as a TXT record in Cloudflare. This record proves to Laravel Cloud that you own the domain.In Cloudflare, set the record name to _cf-custom-hostname (without the domain suffix — Cloudflare appends the domain automatically).
4

Add SSL validation records (if shown)

Laravel Cloud may show _acme-challenge records. These are used to issue your domain’s SSL certificate so your site can be served over HTTPS. Copy them exactly as shown.If the _acme-challenge record is a CNAME, ensure it is configured as DNS only (grey cloud) in Cloudflare. Proxying this record will prevent the SSL certificate from being issued.

​
Wildcard domains and DCV delegation

Wildcard domains (e.g., *.example.com) require a special _acme-challenge record called a DCV delegation record. This record allows Laravel Cloud to automatically issue and renew SSL certificates on behalf of your wildcard domain. If Laravel Cloud shows a DCV delegation record under _acme-challenge, keep it in place and ensure it remains DNS only (grey cloud). Removing or proxying this record will prevent certificate renewals.

​
Troubleshooting

If verification is stuck:
  • Confirm you are editing DNS records in the correct Cloudflare account and zone (website).
  • Confirm record names are not duplicated. A common mistake is entering the full name including the domain, which causes Cloudflare to append the domain again (for example, _cf-custom-hostname.example.com.example.com).
  • If you have multiple DNS providers involved (registrar + Cloudflare + another provider), confirm which one is actually responsible for your domain’s DNS by running dig NS example.com +short.
For more verification troubleshooting, see Verify Domains.