You Bought the Domain. Claude Built the Site. Now Connect Them: A DNS-to-Live-Site Walkthrough.
Michael Sacca•There's a specific afternoon that a lot of you have had by now: you built a landing page with Claude, it looks good, the form works, and then you realize the URL is amazing-unicorn-3f2c1.netlify.app and nobody is typing that into a bar. Meanwhile, the domain you bought months ago — maybe during a fit of enthusiasm, maybe two renewals ago — is sitting parked at a registrar doing absolutely nothing.
The gap between "my site works" and "my site works at mydomain.com" is DNS, and it's the part of AI-native publishing that almost no tutorial covers, because the people writing the tutorials have done it a hundred times and forgot it's terrifying the first time. So here's the whole sequence, end to end, with the step where most solopreneurs stall flagged explicitly.
If you're still choosing where to host the Claude output, start with Landing Page Builders That Accept Your Own Code (and Which Force a Rebuild) — this walkthrough assumes you've picked a host that takes your files as-is.
Step 0: Know what you actually have
Before you touch a single setting, get clear on the two halves of the problem:
- A registrar — where you bought the domain (Namecheap, Porkbun, Google/Squarespace Domains, GoDaddy, wherever). This is who you pay yearly.
- A host — where the Claude-generated HTML lives (Netlify, Vercel, Cloudflare Pages, GitHub Pages, similar). These all have free tiers that are fine for a static landing page.
Your job is to introduce them. There are two ways to do it, and choosing wrong is the first place people burn an hour.
Step 1: Pick your connection method — nameservers or DNS records
Method A: Change nameservers. You tell your registrar "Cloudflare Pages (or Netlify, or whoever) manages my DNS now." The host gives you two nameserver addresses like dns1.p02.nsone.net. You paste them into the registrar's nameserver field, and from then on the host controls everything.
Method B: Keep your registrar's DNS and add records. You leave nameservers alone and manually add an A record and/or CNAME record at the registrar pointing at the host.
Which one? If your domain is only for this one site, Method A is cleaner — the host's dashboard walks you through it, and SSL provisioning usually happens automatically. If you use the domain for email, or you have other subdomains pointing elsewhere, stay with Method B so you don't blow away your MX records in a nameserver switch. Deleting your email's DNS by accident is a rite of passage; skip it.
Step 2: Add the domain in your host's dashboard
In Netlify: Domain settings → Add custom domain → type yourdomain.com. Vercel and Cloudflare Pages have equivalent flows. The host will show you exactly which records it wants. Write them down or leave the tab open — this is your cheat sheet for the next step.
You'll typically see two requirements:
- The apex domain (
yourdomain.com) needs an A record pointing at a specific IP the host gives you (this varies by host — use what your dashboard shows, not a number you find in an old blog post, including this one). - The www subdomain needs a CNAME record pointing at something like
your-site.netlify.apporcname.vercel-dns.com.
Set the apex as your primary and redirect www to it, or the reverse — just pick one canonical version so you don't split your traffic and your future analytics.
Step 3: Add the records at your registrar
This is the mechanical part. Log into your registrar, find the DNS management page (GoDaddy buries it; Namecheap calls it "Advanced DNS"), and add:
Type Host Value TTL
A @ (IP from your host) Automatic or 3600
CNAME www (target from your host) Automatic or 3600
Three notes that save support tickets:
- "Host" or "Name" of
@means the apex itself. Don't typeyourdomain.cominto that field —@is the shorthand. For www, you typewww, not the full URL. - TTL is how long other servers cache the record before checking again. If your host lets you set it, a low value like 300 (five minutes) during setup means mistakes fix themselves fast. Once everything works, you can raise it.
- Some registrars pre-fill junk. Parking pages, "redirect" records, placeholder A records. Delete or edit those rather than adding yours alongside them and hoping the right one wins.
Step 4: The step where almost everyone gets stuck
Here it is: the waiting, and the false alarm it causes.
DNS changes don't take effect instantly. The old record is cached across the internet for anywhere from minutes to the length of your TTL — commonly a few hours, occasionally up to a couple of days depending on what was cached where. During that window, three confusing things can happen:
- Your domain shows the old parked page.
- Your domain shows nothing at all.
- Your browser shows a security warning or "site can't be reached" error even though the host dashboard says the domain check is pending.
Almost everyone hits a variant of #3, panics, assumes they broke something, deletes their records, re-adds them, deletes them again, and resets their propagation clock with every change. Don't. If the host dashboard shows the domain as "verifying" or "pending," and you added the records correctly, the answer is to walk away for a few hours.
Two diagnostics while you wait:
- Use a public DNS lookup tool (there are several free ones — search "DNS checker") to see whether your new A and CNAME records have propagated. Type in your domain, pick record type A, see which locations report the new value.
- Check in an incognito window or a different device. Your own browser aggressively caches both DNS and SSL state.
Step 5: SSL — the certificate arrives on its own, mostly
Once DNS resolves, your host provisions a Let's Encrypt certificate automatically — Netlify, Vercel, and Cloudflare all do this for free with no action from you. The catch is that provisioning starts when DNS points correctly, so the https padlock often shows up a few minutes to a few hours after the domain starts resolving.
If it's been more than a day and you're still seeing "not secure": go back to the host dashboard and check that both the apex and www are added as custom domains, because the most common cause is that one of the two got configured and the other didn't. Also verify your registrar doesn't have an old "SSL/parking" record conflicting with the CNAME.
Step 6: Redirects and the last mile
Two small things that make the difference between "works" and "works well":
- Force HTTPS. In your host's domain settings there's a checkbox (Netlify calls it "Force HTTPS"). Turn it on so anyone typing yourdomain.com gets redirected to the secure version.
- Redirect www → apex (or the reverse), as decided in Step 2. Same settings page.
Then run your page through a speed check, because a landing page you're going to send traffic to should load fast — this overlaps with what breaks first when paid traffic shows up, which we covered in Free Tiers, Audited: What Wix, Carrd, and Framer Actually Block When You're Running Paid Traffic and the audit of the free hosting stack in Build a Website Free With AI: The Zero-Dollar Stack, What You Get, and What Breaks First.
A note on "AI domain hosting"
You'll see that phrase in search results, so let's be honest about it: there is no special hosting category for AI-built sites. A page Claude generated is ordinary HTML, CSS, and JavaScript — it hosts anywhere static sites host. What the AI changed is the build; the hosting is the same free-tier static hosting everyone else uses. Any product marketing itself as "AI domain hosting" is usually a regular host with a prompt box bolted on, which is fine if you like it, but it isn't a requirement. The same goes for ChatGPT-built sites — same files, same DNS, same walkthrough.
The one-paragraph recap
Registrar → decide nameservers vs. records → add domain in host dashboard → add the A record and CNAME it gives you at the registrar → wait (this is the step, be patient) → SSL provisions itself → force HTTPS and redirects → done. Total hands-on time is about twenty minutes. Total wall-clock time is usually two to four hours, almost all of it Step 4. The only real mistake available to you is making more changes while you wait.