Custom Domain for an AI-Generated Website: Step-by-Step
Connect a custom domain for an AI-generated website: buy the name, add DNS records, and fix the errors that stop it from working.
On this page
- What a custom domain for an AI-generated website actually is
- What you need before you connect a domain
- DNS records explained in plain language
- Build it with FromScratch
- How to connect a custom domain to an AI-built site
- Why is my custom domain not working?
- Custom domain vs. a free subdomain: how to decide
- FAQ
Connecting a custom domain to an AI-generated website takes about fifteen minutes once you understand three things: what a domain is, which settings control it, and what to check when it fails. You buy the name from a registrar, add a few DNS records that point it at your published site, and wait for those changes to spread. This guide walks through each step for founders, freelancers and small-team owners who have never touched DNS.
What a custom domain for an AI-generated website actually is
A domain name is the human-readable address people type, such as yourstudio.com. Behind it, your site lives at a public address the builder gives you by default. Visitors see that default address in the browser bar, and it is usually longer and less memorable than the name you would print on a card.
Custom domain vs. the default public URL
The default URL works for testing and early feedback. A custom domain replaces it with a name you own, so the same site looks like a business rather than a project. It also makes sharing easier: a short address on a flyer, an email signature or a social profile reads as more credible than a generic link.
A custom domain does not change what the site does. Your forms, pages and database stay the same. You are only changing the address that points to them.
When you can skip it
You can skip a custom domain for an internal tool your team uses, a prototype you are showing to five people, or a page you will throw away next month. Many people publish to the default URL first, collect feedback, and only then buy a name. This is a sensible order, and it avoids paying for a domain before you know what the site is for.
What you need before you connect a domain
Before you start, check four things. Missing any one of them is the usual reason the process stalls halfway.
- A finished site you are willing to publish. Publishing puts the site live, so review it first, on desktop and on a phone.
- A registered domain. You can register one at any domain registrar, or use a name you already own.
- Access to the DNS settings. The registrar's control panel must let you add or edit DNS records.
- Time for changes to spread. DNS updates are not instant, so plan to check back rather than expecting results in the first minute.
Choosing a domain name
Keep it short, spell it the way people say it, and avoid hyphens and numbers if you can. If you are a freelancer, your own name is usually the safest choice. Check that the extension you want is available and that the name does not clash with an existing business in your market.
Checking who controls your DNS
Domain ownership and DNS control are separate. The registrar you bought the name from usually hosts the DNS settings, but some people delegate DNS to another provider. Log in to the account where you bought the domain and find the section labeled DNS, nameservers or records. If you cannot find it, the registrar's help documentation or support team can point you to it.
If you are buying a domain for a no-code website for the first time, pick a registrar whose dashboard you can navigate without help. You will spend most of your time there, not in the builder.
DNS records explained in plain language
DNS, the Domain Name System, is the internet's address book. When someone types your domain, DNS looks up a record that says where the site is hosted. You do not need to understand the protocol to connect a domain, but you do need to know the record types you will see.
Wikipedia's article on the Domain Name System gives a thorough background if you want more detail.
The two record types you will use most are:
| Record type | What it does | Typical use |
|---|---|---|
| CNAME | Points one name to another name | www pointing to the hosted site |
| A | Points a name to a numeric address | The bare domain (root), such as yourstudio.com |
Use the exact values shown on the publishing screen. Do not copy them from a forum post or an old tutorial, because hosting targets change. The record values are the one part of this process you should not type from memory.
Also leave your existing email records alone. MX records route your email, and if you delete or overwrite them while adding a website record, your inbox stops receiving messages. Add the website records and leave everything else as it is.
Root domain vs. www subdomain
The root domain is yourstudio.com. The www version is www.yourstudio.com. They are technically different names, so each needs its own record. Many people add the www record and forget the root, which produces a site that loads for some visitors and fails for others. Section three below covers how to fix this.
What TTL means for how fast changes show up
TTL, or time to live, is a number that tells resolvers how long to cache a record before checking again. A short TTL means changes spread quickly; a long TTL means old values can linger for hours. If you change a record and still see the old result, the TTL is usually the reason. Wait, then check again, and avoid making several edits in a row, since each one can reset your expectations.
Build it with FromScratch
FromScratch is an AI app builder. You describe what you want in a chat, an AI agent builds it as a React front-end, a Python (FastAPI) back-end and a database, and you see a live preview within minutes. For a landing page like the one below, you can get to a publishable site in one session. If you are new to this approach, the vibe coding guide for non-coders explains the workflow in more detail.
Here is the process from start to finish:
- Sign in and start a new project from the FromScratch home page.
- Describe the site in one message. Be specific about sections, content and the form fields. Vague prompts produce generic pages.
- Review the live preview. Check the headline, services and contact form on both desktop and phone.
- Refine by chatting. Ask for small changes, such as "make the services cards larger" or "add a thank-you message after the form is sent."
- Use version history if something breaks. Every change is saved, so you can restore an earlier version rather than rebuilding.
- Publish to a public URL. Confirm the site loads and the form works at the default address.
- Add your custom domain using the records shown during publishing.
Example prompt and what the agent builds
Paste this into the chat to start:
Build a simple landing page for a freelance photography studio. Include a short intro with a headline, a services section listing portrait, wedding and product shoots, a small portfolio gallery with placeholder images, and a contact form that asks for name, email and preferred date. Keep the design clean and mobile-friendly, then publish it to a public URL so I can connect my own domain.
The agent should produce a headline and intro, three service blocks, a gallery of placeholder images you can swap later, and a contact form with the three fields. Read the result as a visitor would. If a field is missing or a section is in the wrong order, ask for that specific change.
If you later want to take bookings directly, the booking app guide covers how to extend a page like this. For a quick comparison of tools, the AI app builder overview explains what the category covers.
Publishing checklist before you add the domain
Before you touch DNS, confirm the following on the public URL:
- The headline, services and gallery load on a phone and a laptop.
- The contact form submits and you receive the message.
- Placeholder images are replaced with your real work, or clearly labeled as samples.
- Your name, email and location are correct, since visitors will judge the site by them.
Publishing to the default URL first means that if the domain step fails, you still have a working site to point people to.
How to connect a custom domain to an AI-built site
Once the site works at its public address, follow these steps:
- Open the publishing screen in FromScratch and choose the option to use your own domain.
- Enter the domain exactly as you registered it, for example yourstudio.com.
- Copy the records the screen displays. Note the record type, the name and the value for each one.
- Log in to your registrar, open the DNS section, and add each record. Do not delete existing MX or TXT records you did not create for this site.
- Save the changes and wait. Propagation can take minutes or up to a day or more.
- Check the domain in a private browser window. If it loads, test the contact form on the custom address too.
Keep the default URL live until the custom domain works. This avoids a gap where visitors and shared links both fail.
Why is my custom domain not working?
Most failures come from a short list of causes. Check them in this order.
The domain shows a registrar parking page. The record still points to the registrar, not to your site. Open the DNS section again and confirm the record values match the publishing screen exactly. Look for typos, extra spaces, or a second conflicting record for the same name.
The site works on the default URL but not the custom one. DNS has not finished spreading, or a record is wrong. Wait, then recheck the records. If they match and the problem persists after a day, contact support with a screenshot of what you entered.
www works but the root domain does not, or the reverse. Add both versions. The www name and the root name each need a record, and visitors type either one.
The browser shows an old version of the site. Clear your browser cache or try a private window. If a recent change is still missing, check the TTL, since a long TTL keeps old answers in circulation longer than you expect.
The form stops working after you add the domain. Open the custom address and submit a test message. If it fails there but works on the default URL, note the exact error and send it to support.
When you contact FromScratch support, include the domain name, the exact records you entered, the time you made the changes, and what you see in the browser. That information lets the team find the mismatch quickly.
Custom domain vs. a free subdomain: how to decide
A free public URL is fine for testing, internal tools, early feedback and anything you plan to replace. A custom domain makes sense for customer-facing pages, sales material, email signatures and anything you print on a card or a van.
The main cost of switching later is broken links. Anyone who bookmarked or shared the default URL will need the new address. If you expect the site to matter, buy the domain before you start sharing widely. If you are still exploring, FromScratch's free plan lets you publish and test without committing to a name.
For a broader discussion of picking a builder and plan, the best AI app builder guide compares what to look for.
FAQ
Do I need to know code to connect a custom domain?
No. You copy the records shown on the publishing screen into your registrar's DNS settings. The work is careful copying, not programming, so the main risk is a typo.
Can I use a domain I already own?
Yes, as long as you can edit its DNS records. If you own a domain at one registrar but manage its DNS elsewhere, make the change in the place where the DNS is actually controlled.
How long does it take for a custom domain to work?
DNS changes can take anywhere from a few minutes to a day or longer to spread, depending on the TTL and the provider. Keep the default URL live while you wait so visitors are not left without a working address.
Will my site go down when I switch to a custom domain?
It should not, if you keep the default URL running until the custom domain loads correctly in a private window. Switch your shared links only after both the root and www versions work.