QAlaunch

Bolt.new custom domain not connecting: causes and fixes

A Bolt.new custom domain fails to connect when the project is not published yet, the records do not point at site-dns.bolt.host, an AAAA record was used, or the domain is still attached to an old Netlify site. Publish, then set the root to an ALIAS, ANAME or flattened CNAME and www to a CNAME, both pointing at site-dns.bolt.host as Bolt's docs describe. Remove the domain from any old host and check the Status column in Domains & Hosting after a few hours.

Opens your site in a real browser on desktop and phone. Free, about two minutes, no signup. Full report from $19.

What you'll see

In Bolt you see a warning that another project is already using the domain, that it is in use on Netlify, or that ownership cannot be verified. Or the domain seems connected but visitors get an SSL warning or your old site. Custom domains are a paid Bolt feature, so the option may also be missing entirely on a free account.

Why it happens

1. Record type or target is wrong

Bolt's help center asks for a CNAME on www and an ALIAS, ANAME or flattened CNAME on the root, all pointing at site-dns.bolt.host. Many registrars default to an A or AAAA record, and Bolt warns that AAAA will not connect the domain.

2. Still claimed by an old Netlify site

Earlier Bolt deploys went to Netlify. If the domain is still added to that Netlify site, Bolt reports it as already used, and a domain bought through Netlify may need Netlify support to release it.

3. The project is not published

Bolt only lets you connect a domain to a published project. Before the first publish, the option to connect a domain does not appear.

4. DNS half finished, so SSL fails

If www points at Bolt but the root still points elsewhere, or the TXT record for a subdomain is missing, the certificate cannot be issued for every name and visitors see a security warning.

How to fix it

  1. Publish the project, then open the gear icon > All project settings > Domains & Hosting and click Connect a domain you own. Enter the domain and click Verify and add domain, keeping the DNS screen open.
  2. At your registrar or DNS host, set www as a CNAME to site-dns.bolt.host and the root as ALIAS, ANAME or flattened CNAME to site-dns.bolt.host. Confirm the current target in Bolt's own DNS screen before saving, since hosting targets can change.
  3. Delete any AAAA records and any old A or CNAME records on those names that point at Netlify or a previous host.
  4. For a subdomain such as app.yourdomain.com, add the TXT record Bolt shows and click Verify and add subdomain; that record usually becomes visible within minutes.
  5. If Bolt says the domain is in use, log in to Netlify (or the other service), open its domain management for the old site and remove the domain, then reconnect it in Bolt.
  6. Return to Domains & Hosting and read the Status column. Most domains connect within a few hours; Bolt says some take up to 24. Check status.bolt.new if nothing moves.

Prompt to paste into Bolt.new

No code change is needed for this; it is a DNS fix. If you want a checklist, ask Bolt: "List the DNS records my custom domain needs for Bolt hosting and anything I should remove from my old Netlify site."

How to check it's fixed

  • Look up the root and www on a public DNS checker; both should resolve through site-dns.bolt.host with no AAAA records.
  • Open https://yourdomain.com and https://www.yourdomain.com in a private window on a laptop and a phone; both should load your Bolt site with no certificate warning.

What a QAlaunch scan shows for this

  • A certificate error or failed load when the scan opens the domain over HTTPS.
  • The wrong site in the screenshots, such as your old Netlify version or a registrar page.
  • Scanning root and www separately shows whether both names reach the new site; the scan does not read DNS itself.

See exactly what a full report contains in the sample report.

Frequently asked questions

My registrar does not offer ALIAS or ANAME. What now?

Some registrars only support A and CNAME records. You can move DNS hosting to a provider that offers flattened CNAMEs, such as Cloudflare, and keep the registration where it is, or ask your registrar's support what they offer at the root.

I moved from Bolt hosting to Netlify. Why did the domain stop working?

Domains do not move automatically between Bolt and Netlify. Reconnect it in Netlify's Domain management, and remove it from Bolt so the two do not compete.

Do I need a paid Bolt plan for a custom domain?

Yes. Bolt's help center says Free and Pro can both publish to a .bolt.host address, while custom domains are for paid plans.

Done for you · not automated

Rather have a QA engineer test it by hand?

If this is a site you're launching or handing to a client, I'll go through it by hand, including the Bolt.new-specific issues a scan can't reach, like logged-in flows.

$299one-time · 3 business days
  • Up to 10 key pages tested by hand, not a scan
  • Every flow a customer uses: forms, sign-up, checkout, booking
  • Real mobile and desktop browsers
  • A written report in plain language, with screenshots
  • A 15-minute call to walk you through it
  • 10 years of professional QA experience

Tell me about your site and I'll reply personally, usually the same day.

No payment now. I'll confirm scope and price first.

Related fixes

More for Bolt.new: all Bolt.new fixes · Bolt.new testing · 9 bugs every AI-built site ships with

Written by Waqas Ahmad, QA engineer with 10 years of professional testing experience. Last checked October 26, 2026.

Sources: Bolt help center: connect a domain · Bolt help center: domain issues