Custom domain not working

Symptom

• The domain shows an "Action needed" badge in the page editor, with DNS records to add.
• The custom domain returns "DNS_PROBE_FINISHED_NXDOMAIN" or similar.
• The page loads on HTTP but HTTPS shows a certificate error.

Why it happens

• The DNS record is missing, misspelled, or points to the wrong target.
• DNS has not finished propagating (can take up to an hour).
• You added a CNAME at the root domain, where most providers reject it. Root domains need an A record.
• An existing A or CNAME record on the same name conflicts with the new record.
• Cloudflare proxy is on (orange cloud); for verification it must be off (grey cloud) initially.

How to fix

1. Open the booking page editor, go to the Pro features tab, and compare the records listed under Custom Domain against what is in your DNS provider. Add exactly what the editor shows.
2. For a subdomain, confirm the CNAME points at the right host:
   shell

   dig +short CNAME book.yourcompany.com
   # expected: custom.timetuna.com.

3. For a root domain, use an A record (not a CNAME):
   shell

   dig +short A yourcompany.com
   # expected: 76.76.21.21

4. Remove any conflicting record on the same name. A CNAME cannot coexist with an A or AAAA record on the same host.
5. If your DNS is behind Cloudflare, switch the record's proxy to DNS only (grey cloud) while TimeTuna issues the certificate. You can re-enable the proxy after the certificate is live.
6. Wait 10 to 60 minutes after the DNS change, then click Check DNS Status in the editor again.

Still not working?

Open the chat in the bottom-right with the full domain name, the output of dig yourdomain, and a screenshot of your DNS provider's record list.