BaseStack help article
Custom domain verification troubleshooting
Fix common reasons a paid custom domain does not verify or serve the expected site.
Overview
Most custom domain issues come from DNS records that have not propagated yet, records added to the wrong hostname, or older records that conflict with the BaseStack setup.
Check these first
Steps
- Confirm your BaseStack plan includes custom domains.
- Confirm the site is already published.
- Check that the requested hostname exactly matches the DNS hostname.
- Look for duplicate A, AAAA, CNAME, forwarding, or parking records on the same hostname.
- Wait and retry if the record was added recently.
What to send support
Key points
- The BaseStack site slug or page title.
- The exact domain or subdomain you are connecting.
- A screenshot of the DNS records for that hostname.
- The DNS provider name, such as Cloudflare, GoDaddy, Namecheap, or Squarespace.
- Any error message shown in the custom domain panel.
Hide private account details
Screenshots should not show registrar passwords, billing details, recovery codes, or unrelated private domains.