Quick answer: Connecting a custom domain is three decisions and two copy-pastes: choose the domain, choose root or www as your one true URL, and decide what happens to anything already living on that domain (especially email). Then add the domain in settings, copy the records it gives you into your registrar, and wait minutes-to-hours for the internet's phone book to update. The padlock (SSL) issues itself automatically — never buy one from a registrar upsell.
The domain step is where website launches go to stall. The site is done, the copy is reviewed — and then someone says "now just update your DNS" and hands you a bowl of vocabulary soup: A records, CNAMEs, nameservers, propagation, SSL. It sounds like system administration. It's actually a change-of-address form.
Here's the whole thing in plain language: the mental model, the three decisions to make before touching anything, the two copy-pastes, and what to do in the rare case it doesn't immediately work.
The mental model: a name, a phone book, and a building
Three separate things are involved, and most confusion comes from blending them:
- Your domain (yourbusiness.com) is a name you rent annually from a registrar — the company where you bought it. You own the name no matter where your website lives.
- DNS is the internet's phone book: it answers "where does this name point?" The listings in it are called records.
- Your website is the building. Connecting a domain doesn't move the building — it updates the phone book so the name points at it.
That's the entire operation: update two listings in a phone book. The vocabulary is bureaucratic, not technical — an A record points a name at an address, a CNAME points a name at another name, and you will be told exactly which to set and to what. You never have to compose one from scratch.
Three decisions before you touch anything
If you already own one with history — customers know it, links point to it, it's on the van — keep it; domain age and existing links are SEO equity you don't throw away. Buying new? Be pragmatic: the .com your customers will guess beats the clever alternative they won't, and a pronounceable name beats a pun you have to spell over the phone.
yourbusiness.com and www.yourbusiness.com can both work, but exactly one should be the primary domain — the version every visitor ends up on, with the other redirecting to it. It barely matters which you pick; it greatly matters that you pick. Search engines, analytics, and shared links all consolidate on the primary — a site split across two versions of itself dilutes everything the SEO fundamentals build.
The classic self-inflicted outage: changing more than asked and taking your email down with the old website. Your domain's phone book has separate listings for web and mail — connecting the website only requires touching the web listings. The rule that prevents 90% of domain disasters: change exactly the records you're given, leave every other record alone, and never change nameservers when you were asked to change records.
The connection: two copy-pastes and a wait
The actual flow:
- Add the domain in Settings → Domains. The workspace shows you the exact records to set — names and values, ready to copy.
- Paste them at your registrar. Log in where you bought the domain, find DNS settings (sometimes "DNS management" or "zone editor"), and add or edit the records to match. Character-for-character — a trailing dot or a stray space is the most common failure.
- Wait for the phone book to update. "Propagation" just means the world's DNS servers refreshing their copies. Officially up to 48 hours; in practice usually minutes to a couple of hours. The status check tells you when it's verified — watch that, not your browser's cache.
SSL: the padlock takes care of itself
The padlock in the address bar — the certificate that makes your site https and keeps browsers from warning visitors away — issues and renews automatically once your domain verifies. There is nothing to buy, configure, or remember annually. Which makes this a good moment for consumer advice: registrars love selling SSL certificates at checkout, and for a site on a managed platform that purchase is buying a thing you already get free, forever. Decline it. (Same goes for most of the checkout upsell column, with the arguable exception of privacy protection on your contact details.)
After connecting: make the primary domain the only domain anyone sees
Once verified, finish the consistency pass the primary-domain guide describes: alternates redirect to the primary, and the primary is the URL in your campaigns, forms, printed materials, and ad accounts. If you're switching from an old domain, keep it connected and redirecting — every old link, bookmark, and search result keeps working, and its equity flows to the new name. And changing an established primary is a decision, not a whim: ads, emails, print, and years of links point at it. Possible, occasionally right, never casual.
When it doesn't work: the usual three
The troubleshooting guide walks the diagnostics, but nearly every stuck connection is one of three things:
- A typo in the record. Compare character-for-character against what settings showed you — value, name, and type. This is the most common by a mile.
- An old record still competing. If the domain pointed somewhere before, the previous listing may still exist alongside your new one. There should be exactly one answer for each name — delete the stale one.
- Impatience. If the records are right, time fixes the rest. Check status after an hour, not every ninety seconds — and remember your own browser caches aggressively; the status check is the truth, your browser is a rumor.
Past those three, it's usually a registrar quirk (some require an @ where others want a blank name field) — the troubleshooting guide covers the common dialects, and support has seen your registrar before.
Key takeaways
- A domain connection is a change-of-address form: update two listings in the internet's phone book.
- Decide first: which domain, root or www as the one true URL, and what else (email!) lives on the domain.
- Change exactly the records you're given and nothing else: and records, never nameservers.
- SSL issues and renews itself: decline the registrar's certificate upsell.
- Set the primary domain, redirect the alternates, and use the primary everywhere: print included.
- When it's stuck: typo, stale competing record, or impatience — in that order of likelihood.
Frequently asked questions
Do I have to buy my domain through Faster?
No — bring a domain from any registrar. Ownership stays with you at the registrar; the connection just points the name at your site. That separation is healthy: your name isn't tied to any single provider, including us.
Will connecting my domain break my email?
Not if you follow the one rule: only add or edit the web records you're shown, and leave the mail records (MX and friends) untouched. Email breaks when people change nameservers or "clean up" records they don't recognize. When in doubt, change nothing extra and ask.
How long does the whole thing actually take?
Five minutes of doing and usually under an hour of waiting. The 48-hour figure is the worst-case ceiling for the phone book to update worldwide; most connections verify before you've finished the coffee. Plan a launch day around hours, not days.
Root domain or www — is one actually better?
Functionally they're equivalent for a small business; www has minor technical conveniences at large scale, the bare root looks cleaner on a business card. Pick by taste, set it as primary, redirect the other, and never think about it again — the consistency is the value, not the choice.
Can I connect more than one domain to the same site?
Yes — the common pattern is the .com plus defensive variants (the .net, the common misspelling, the old business name), all redirecting to one primary. They catch strays; they should never serve the site independently, or you're back to diluting your one true URL.
If the site is ready and the domain step is what's between you and live, block thirty minutes: make the three decisions, do the two copy-pastes, and let the launch checklist take it from there. The soup was never that deep.