Skip to main content
Laravel Cloud shows the exact DNS records you need for your domain. The most common verification failures come from entering the right record with the wrong name format. This usually happens when a full domain name (like _cf-custom-hostname.example.com) is pasted into a provider’s host field that only expects the first part (like _cf-custom-hostname).

​
General rule of thumb

When your DNS provider asks for a “host” or “name,” it usually wants only the part before your domain — not the full domain name. Your provider appends the domain automatically:
  • For www.example.com, enter www
  • For _cf-custom-hostname.example.com, enter _cf-custom-hostname
  • For _acme-challenge.example.com, enter _acme-challenge
  • For example.com, many providers use @ (or leave the host blank)
After saving a record, always re-open it in your provider’s dashboard and confirm the final, assembled name matches what Laravel Cloud shows. This is the single most effective way to catch formatting mistakes early.

​
Provider-specific notes

Unlike most providers, Route 53 accepts fully qualified record names — meaning you can paste the complete name from Laravel Cloud (for example, _cf-custom-hostname.example.com) directly into the name field. Route 53 may add a trailing dot (e.g., _cf-custom-hostname.example.com.). This is standard DNS formatting and is expected.If you are not sure you are editing the correct hosted zone, confirm which nameservers are authoritative for your domain:
dig NS example.com +short
The output should match the nameservers listed in your Route 53 hosted zone.
GoDaddy’s DNS editor uses a “Host” field that expects only the subdomain portion. For example, if Laravel Cloud shows _cf-custom-hostname.example.com, enter _cf-custom-hostname — GoDaddy adds .example.com for you.After saving, GoDaddy displays the full record name. Confirm it matches the record name shown in Laravel Cloud exactly, with no repeated or missing parts.
Namecheap’s DNS editor uses a “Host” field that expects only the subdomain portion. For example, if Laravel Cloud shows _acme-challenge.example.com, enter _acme-challenge — Namecheap adds the domain automatically.For root-domain records (i.e., records for example.com itself), use @ as the host value.
Squarespace (which acquired Google Domains) has its own naming conventions that can differ from the fully qualified names shown in Laravel Cloud. In most cases, you should omit the .example.com suffix when entering record names — Squarespace appends it for you, similar to GoDaddy and Namecheap.
If your domain is using Cloudflare nameservers, see the Cloudflare DNS Guide.

​
Verify your DNS records

Once you have added your records, you can confirm they are visible on the internet by running the following commands in your terminal. Replace example.com with your actual domain: 
# Check which nameservers are responsible for your domain
dig NS example.com +short

# Check if your origin (A / CNAME) records are resolving
dig A example.com +short
dig CNAME example.com +short

# Check ownership verification and SSL validation records
dig TXT _cf-custom-hostname.example.com +short
dig TXT _acme-challenge.example.com +short
dig CNAME _acme-challenge.example.com +short
If a command returns no output, the record either has not been created yet or has not finished propagating. DNS changes can take anywhere from a few seconds to several minutes to become visible.