How to Set Up a Custom Domain (for Your Landing Page, Funnel, or Site)

Published June 18, 2026

Disclosure: Some links below are affiliate links. If you sign up through them we may earn a commission at no extra cost to you. We only recommend tools we'd genuinely suggest to a friend. See our full disclosure.

You’ve built a landing page or funnel, it’s live on a free subdomain like yourname.systeme.io/offer, and it works. At some point you’ll want it to live at your own address instead — yourname.com — because a custom domain looks more credible, is easier to remember, and is yours to keep no matter which tool you use later.

This is a plain-English walkthrough of doing exactly that: buying a domain and connecting it to your page. It sounds technical because of the jargon — DNS, A records, CNAME, nameservers — but the actual steps are short and you only do them once. I’ll explain what each piece means so you’re not blindly pasting things, and I’ll flag the few mistakes that make people waste an afternoon. This is the companion to how to create a free landing page — that guide gets your page live; this one gives it a real address.

First: do you even need one yet?

Honestly, not on day one. A free subdomain (yourname.tool.com/offer) loads instantly, takes payments, captures emails, and converts just as well as a custom domain for someone who arrived from a link they trust. Plenty of real businesses run their first offer entirely on a free subdomain.

A custom domain is worth adding once one of these is true:

• The page is live and converting, and you want to invest in the brand around it.
• You’re putting the link in places where it’s judged — business cards, ads, a pitch, your email signature — where yourname.systeme.io looks less established than yourname.com.
• You want an address that’s portable — if you switch page builders later, a custom domain moves with you; a free subdomain doesn’t.

If none of those apply yet, launch on the free subdomain, send traffic, and come back to this when it’s earning. Spending an afternoon on DNS before you have a single visitor is the wrong order.

The mental model: two separate things connected by a phone book

The single biggest source of confusion is thinking a domain and a website are one purchase. They’re not. There are two distinct pieces:

1. The domain — the address, e.g. yourname.com. You rent it (yearly) from a registrar.
2. The host — the place the address points to. For a landing page, this is your page builder (Systeme.io, etc.); for a website it’s a web host. The host holds the actual page.

Connecting them is the job of DNS — think of it as the internet’s phone book. When someone types yourname.com, DNS looks up “where does this name actually live?” and sends the browser there. “Pointing your domain at your page” just means adding the right entry to that phone book.

So the whole task is three moves: (1) buy the domain, (2) tell your page builder you want to use it, (3) add the DNS records the builder gives you. That’s it.

Step 1: Buy the domain from a reputable registrar

A registrar is the company you rent the domain name from. Pick a well-known, straightforward one and buy directly — avoid getting your domain bundled into some other service where it’s awkward to manage later.

When you buy:

• Choose the name carefully — short, easy to spell, easy to say out loud. (If you haven’t settled on one yet, how to name your online business walks through picking a good, available name without losing weeks to it.) A .com is still the most trusted and memorable for most people; other extensions are fine if the name fits, but don’t pick a weird extension just because the .com is taken if it makes the address confusing.
• Decline the upsells you don’t need. Registrars push add-ons at checkout. You almost never need their email hosting, site builder, or “SEO” extras to connect a domain to an existing page. Domain privacy (WHOIS privacy) is the one add-on usually worth keeping — and many registrars now include it free — because it keeps your personal contact details out of the public domain record.
• Check the renewal price, not just year one. Many registrars advertise a cheap first year that renews at a higher rate. Know what you’ll actually pay next year before you buy.

You don’t need to buy hosting from the registrar. Your landing page tool is already doing the hosting — you only need the name.

Step 2: Tell your page builder you want to use the domain

Before you touch any DNS settings, go into the tool that hosts your page and find its custom domain (sometimes “domains” or “add a domain”) section. In an all-in-one platform like Systeme.io, this lives in the account or settings area; on its paid plans you add your own domain and assign your pages and funnels to it. (Custom domains are one of the standard upgrades that sit on paid tiers across these tools — the free plan keeps you on the subdomain, which is exactly why launching free first makes sense. Check the current plan details before you commit, since providers change what’s included.)

When you add the domain there, the tool will show you the exact DNS records to create — usually one or two values, specific to that platform. Don’t guess these. Copy them from your builder’s instructions, because the precise record type and value differ from tool to tool. Keep that screen open; you’re about to paste those values into your registrar.

Step 3: Add the DNS records at your registrar

Back in your registrar’s dashboard, find the DNS settings (sometimes “DNS management,” “advanced DNS,” or “manage records”) for your domain. You’ll add the record(s) your page builder gave you. The three kinds you’ll run into:

• A record — points a name at a numeric server address (an IP, like 12.34.56.78). Builders often have you point the root domain (yourname.com, shown as @) at their IP with an A record.
• CNAME record — points a name at another name rather than a number. The www version (www.yourname.com) is commonly set as a CNAME pointing to your builder’s address. CNAMEs are also how many tools verify and route subdomains.
• Nameservers — the heavier option: instead of editing individual records, you hand the entire domain’s DNS over to another provider by changing its nameservers. Some platforms prefer this; only do it if your builder specifically tells you to, because it moves all DNS control to them.

Practically: open the record list, add a new record of the type your builder specified, put their value in the value/target field, and save. If the tool gave you both a root (A) and a www (CNAME) entry, add both. Delete or replace any old conflicting record pointing the same name somewhere else — two records fighting over the same name is a classic reason it “doesn’t work.”

Step 4: Wait for propagation (this is the part that feels broken)

After you save, your domain often won’t work immediately — and that’s normal, not a mistake. DNS changes have to spread across servers worldwide, which can take anywhere from a few minutes to roughly 24–48 hours (usually much faster than the worst case).

So if you type your domain right after setting it up and it doesn’t load, don’t start changing things in a panic — that’s how people break a setup that was actually fine. Give it time. Come back in an hour, then a few hours later. Most of the second-guessing and “I think I did it wrong” happens in this waiting window when nothing was wrong at all.

While you wait, your page builder usually also issues an SSL certificate automatically so your domain loads over secure https:// with the padlock. That can take a little extra time after the DNS resolves. A page that loads but shows a “not secure” warning for the first short while is often just the certificate still being issued — give that a little longer too before assuming a problem.

Step 5: Pick www-or-not, and test like a stranger

Once it resolves, decide on your canonical version — yourname.com or www.yourname.com — and make the other redirect to it. Most builders have a one-click setting for this. It doesn’t matter which you pick; what matters is that both lead to the same place so you don’t look inconsistent or split your links.

Then test it properly, the way a visitor would:

1. Open the live custom domain in a fresh/incognito window (your browser may cache the old subdomain).
2. Try both yourname.com and www.yourname.com — confirm both load and land on the right page.
3. Check the padlock shows (secure https://).
4. Run through the actual page on your phone — submit the form, confirm the thank-you page and delivery still work end to end.

If you moved a page that was already getting traffic, point your old subdomain link at the new domain where you can, and update the link everywhere you’ve shared it.

Common mistakes that cost people a day

• Changing DNS, then panicking 5 minutes later. Propagation is the number-one false alarm. Wait before you touch anything.
• Pasting the wrong record type. An A record and a CNAME are not interchangeable — use exactly what your builder specified, in the field they specified.
• Leaving a conflicting old record in place. If a name already points somewhere, remove that record before (or instead of) adding the new one. Duplicates fight.
• Buying hosting you don’t need. Your page builder is the host. You only needed the domain name.
• Forgetting the renewal. Set the domain to auto-renew, or put a reminder in your calendar — a lapsed domain takes your live page down.
• Splitting www and root. Pick one as canonical and redirect the other.
• Judging it on the editor preview. Always test the real live domain in a fresh window, not the builder’s internal preview.

The honest verdict

Setting up a custom domain is a one-time, maybe-fifteen-minutes-of-actual-work job that feels harder than it is, mostly because of jargon and the waiting. Strip away the words and it’s three moves: buy the name, tell your page builder to use it, paste the DNS records it gives you — then wait for propagation and test in a clean window.

The right time to do it is after your page is live and proving itself, not before. Launch on the free subdomain (see how to create a free landing page), point real traffic at it, and add the custom domain once it’s earning its keep — at which point an all-in-one tool like Systeme.io lets you attach the domain and keep your pages, emails, and funnel in one place. The domain is the part that’s truly yours and portable; everything else you can change later.