I built my website in a weekend. Why is getting it on my own domain so hard?

It is Sunday night. You started Friday with an idea and a builder, and now there is a real website on your screen. It has your logo, your services, a contact form, even a nice photo of your work. You send the link to a friend and they say it looks great.

Then you look at the link. It is something like yourproject.netlify.app or a long address ending in the builder’s name. Not yourbusiness.com, the domain you bought two years ago and have been paying for ever since.

So you open your domain account. There is a page full of records with names like A, CNAME, MX and TXT. Your host’s help article says to “point your DNS.” Another article says to “change your nameservers.” You are fairly sure one wrong move could take down your email, and you are not wrong.

This is the moment a lot of people stall. Not because they are not capable, but because nobody explained the pieces.

What is actually going on

There are three separate things involved, and they are often with three separate companies.

• Your registrar is where you bought the domain. Think of it as the deed to your address.
• Your host is where the website files actually live. Netlify, Vercel, the builder’s own hosting, and similar services all play this role.
• DNS (the Domain Name System) is the directory that connects the two. It tells the internet, “when someone types this domain, send them to that server.”

Your site works on the builder’s address because the host set up that address for you automatically. Your own domain does not work yet because its DNS still points somewhere else, or nowhere at all.

Records versus nameservers

There are two ways to connect a domain, and this is where most of the confusion lives.

1. Edit individual records. You stay with your current DNS provider (often your registrar) and add or change the specific records your host gives you. Your other records, including email, stay untouched.
2. Change nameservers. You hand the entire DNS directory over to your host. It is clean and simple, but your host starts with its own set of records. Anything you had before, like email, has to be recreated there.

Changing nameservers without copying your email records first is the single most common way people accidentally break their business email.

The www question

yourbusiness.com and www.yourbusiness.com are technically two different addresses. Each needs its own record. Usually the bare domain (often called the apex or root) uses an A record or a special alias record, and www uses a CNAME. Your host will then pick one as the main address and redirect the other to it. If you only set up one, half your visitors may land on an error.

The padlock

SSL (the certificate behind the padlock and the https in your address) is usually free and automatic on modern hosts. But the host can only issue it after it confirms your domain points to it. So if DNS is wrong or still updating, you may see a security warning. That is a symptom, not a separate problem.

Propagation

DNS answers get cached around the internet for a period set on each record, called the TTL (time to live). After you make a change, some people may see the new site right away while others still see the old one. This usually settles within minutes to hours, and occasionally takes up to a day or two.

What to do right now

You can absolutely do this yourself. Go slowly and in this order.

1. Write down where everything lives. Note your registrar, your host, and who handles your email (Google Workspace, Microsoft 365, or your registrar’s own email, for example).
2. Take a screenshot of your current DNS records. Every single one. This is your undo button. Pay special attention to MX records (they route email) and TXT records (they often hold email authentication and verification settings).
3. Add your domain inside your host first. Most hosts have a “custom domain” area. Enter both the bare domain and the www version. The host will show you exactly which records it expects.
4. Prefer editing records over changing nameservers, unless you are confident about recreating your email records. Add or update only the records your host asked for.
5. Remove conflicting web records. If an old A record or CNAME for the same name points to a previous site or a parking page, it can fight with the new one. Remove only the conflicting web record, never the MX records.
6. Wait, then check. Give it an hour. Visit both versions of your domain in a private browser window. Look for the padlock.
7. Send yourself a test email. Send to your business address from a personal account and reply back. If both arrive, your email survived the move.
8. Update the site itself. Some builders and apps store the site’s address in settings, login redirect lists or form tools. Replace the builder address with your real domain wherever it appears.

If something looks wrong after a day, do not keep changing records at random. Compare what you have against what your host asked for, character by character. A missing dot or an extra space is a surprisingly common culprit.

When to hand it off

Some setups are genuinely tangled. The domain is with one company, email with another, an old site is still half-connected somewhere, and the person who set it all up years ago is no longer around. That is where a calm second pair of hands saves you a weekend.

At AftUp, getting your site live on its own domain is included in the first month of every plan. We map where everything lives, back up your existing records, connect the domain and www, confirm the certificate, and verify that your email still flows before we call it done. You keep full ownership of your domain and accounts, and we work inside the tool you already used, so nothing gets rebuilt.

You can see how we approach this on our hosting and domains page, or read more about launch help if you just want the site live and working. When you are ready to keep it that way, our plans cover the monitoring and small fixes that come after launch.

The short version

• Your registrar holds the domain, your host holds the site, and DNS connects them.
• Edit records when you can. Change nameservers only if you recreate email records too.
• Set up both the bare domain and www.
• The padlock appears on its own once DNS is right.
• Screenshot everything before you touch it, and test your email after.

If you would like someone to look over your setup before you flip the switch, send us your URL for a free site check and we will tell you what we see.