How to Connect a Custom Domain to Your AI-Built Site

Your AI-built site is deployed and living on an address like your-project-random-words.platform.app. It works, but it doesn't feel like yours. Pointing your own domain at it is the last mile — and the one where people get nervous, because DNS is explained everywhere in acronyms and almost nowhere in English.

Here's the whole process in one sentence: you buy a domain, your deploy platform tells you exactly which DNS records to create, you create them at your registrar, and then you wait while the internet notices. Everything below just unpacks that sentence.

A record vs CNAME, without the jargon

DNS is a phone book: names get translated to destinations. Only two entries matter for this task.

An A record points a name directly at an IP address — a number like 203.0.113.7. It's the raw "this name lives here" record.

A CNAME points a name at another name, delegating the lookup. "www.yoursite.com is whatever app.platform.com is." This is why platforms prefer CNAMEs: if their infrastructure changes, every customer's setup keeps working without edits.

The wrinkle is the distinction between the apex domain (yoursite.com) and the www subdomain (www.yoursite.com). The apex can't always use a CNAME due to old rules in how DNS works, so registrars offer workarounds under names like ALIAS or ANAME or flattening. You don't need to understand the machinery — you need one habit: copy exactly what your deploy platform's dashboard shows for each hostname, because it has already made these decisions for you.

Add the domain in your platform first

Do it in this order. In your deploy platform's settings, find domains (or "custom domains") and add yoursite.com and usually www.yoursite.com as two entries. The platform responds with precise instructions: this hostname gets an A record with this value, that hostname gets a CNAME pointing here.

Then go to your registrar's DNS settings and add those records exactly as shown — right type, right host, right value. Most confusion in this step comes from freelancing: inventing values instead of copying them, or adding an A record where the platform asked for a CNAME. Copy, paste, save.

The SSL wait

Once DNS resolves, your platform requests an SSL certificate so visitors get the padlock and https://. This issuance is automatic but not instant — it commonly takes from a few minutes up to a few hours after DNS propagates. During that window http:// may work while https:// throws a certificate error, which looks alarming and is normal. Don't delete and re-add anything during the wait; that restarts the clock.

The classic "site still blank" mistake

You've added everything correctly, visited your shiny new domain, and gotten... nothing. Before assuming catastrophe, walk the short list:

• Propagation takes time. DNS changes spread across the internet over minutes to a couple of days depending on cached records. Your own machine may be caching the old answer stubbornly; a different device or network often sees the new site sooner.
• Check what actually propagated, not whether the site loads: free DNS lookup tools will show whether your new records are visible publicly yet.
• Distinguish DNS problems from empty-deploy problems. If the domain loads something — even a platform error page — DNS worked and the deployment itself needs attention. If nothing resolves at all, it's still DNS.
• Hard-refresh before concluding anything. Browsers cache aggressively.

Nine times out of ten, waiting an hour fixes what looked broken.

Our guides on deploying an app built with AI, building a waitlist landing page with AI, and building a landing page with an AI agent cover the steps on either side of this one.

This is also where having your build environment on your desktop pays off: meshcode runs natively on Mac and Windows, so when something about the deployed site looks wrong, an agent session sits next to your terminal and browser, reading the actual project files rather than guessing through a chat window. Describe the symptom in plain language and fix it in the same place you built the thing.

👉 Download meshcode — Mac, Windows