A custom domain puts your own address, such as shop.yourname.com, in the browser bar instead of a platform address, and it takes five jobs: buy or choose the domain, decide between a root domain and a subdomain, add the DNS records your storefront host gives you, wait for the change to spread, and check that HTTPS works. Most of the work is a few records at your registrar and about an hour of patience. This guide walks through all of it for creators who sell e-books, courses, templates or mentoring, in plain words and in the order you will do it.
If you sell educational products, the address is part of the product. Buyers decide in seconds whether a page feels like a real school or a side project. At BibliOWLteca we build storefronts for exactly this kind of seller, so the sections below are written from the creator's side of the table.
TL;DR
- A custom domain replaces a platform address with one you own, which makes your storefront easier to remember and keeps your brand and search visibility under your control.
- Before you start, you need a published storefront, a domain you own or can buy, access to its DNS settings, and a decision about the root domain or a subdomain.
- Use an A record (or ALIAS) for the root and a CNAME for
wwwor any other subdomain, then wait: most changes show within hours, and full propagation can take up to 48 hours. - Test both versions of the address in a private window, confirm HTTPS shows no warning, and make one version redirect to the other.
- If it fails, look for a conflicting record, a record on the wrong host, a proxy switched on, or a CAA record blocking the certificate.
Table of Contents
- What a custom domain does for a creator's storefront
- What to have ready before you connect anything
- Root domain or subdomain: choose before you build links
- The DNS records you will actually use
- Connecting the domain, step by step
- How long it takes, and how to check it
- When verification fails
- Practical rules that save creators trouble
- Our view: your address belongs to your brand, and the platform should not cost you while you build it
- Build your branded storefront with BibliOWLteca
- FAQ
- Sources
What a custom domain does for a creator's storefront
A custom domain replaces the default address your storefront gets with one you choose and own. One platform's help centre describes the benefits as an address that is easier to remember, a stronger business identity, and search visibility consolidated under a domain the business controls. For an educator that last point matters more than it sounds. Every link a student shares, every podcast mention and every guest post you write builds the reputation of the address it points to. If that address belongs to someone else, the reputation is rented.
There are three practical reasons creators care.
Trust at the moment of payment. A learner about to enter card details looks at the address bar. learn.yourname.com reads as a school. A long platform address reads as a listing.
Portability of your audience. Printed handouts, slide decks, podcast show notes and book back matter all carry your address. If you ever change tools, a domain you own keeps working because you simply point it somewhere else.
One address for everything. You can use the same brand across your storefront, your email and your social profiles, so a buyer who remembers one thing finds all of it.
The branding side of this is bigger than the domain. If you are still deciding on a name, colours and tone for your school, our notes on building a scalable online store for digital education cover the structure that sits behind the address.
What to have ready before you connect anything
The same short list applies whichever platform hosts your storefront. Published help documentation lists the prerequisites as a published site, a domain you own or can buy, access to the domain's DNS settings, knowing whether the domain already hosts a website or business email, and completed company and contact details. Translated to a creator's situation:
- A storefront that is live. Publish at least your first product, so you can test the real journey once the domain is connected.
- A domain you control. You need the login of the account where it is registered, called the registrar. If a web designer or a friend bought it for you, ask them to transfer the account or add you as a manager before you start.
- Access to the DNS panel. DNS is the phone book of the internet: a set of records that tell browsers which server answers for your name. Your registrar, or a separate DNS provider if you moved your nameservers, has a page where you add and edit those records.
- A check for existing services. If the domain already runs a website or your email, changing the wrong record can take those down. Note every record currently listed, or take a screenshot, before you change anything.
- Your business details. Name, contact email and the legal information you need on checkout pages, so buyers see a complete page the moment the new address goes live.
Take the screenshot seriously. It is the one step that turns a mistake from a crisis into a two-minute fix.
Root domain or subdomain: choose before you build links
A root domain (also called the apex or naked domain) is yourname.com. A subdomain sits in front of it: www.yourname.com, shop.yourname.com, learn.yourname.com. Both can show your storefront, and the choice shapes the records you add.
When the storefront is the main thing you do, the root domain with www redirecting to it (or the reverse) is the cleanest. When you already have a personal website, a blog or a speaker page at the root, a subdomain keeps them apart: the website stays where it is and the storefront lives at shop.yourname.com or courses.yourname.com.
Whichever you choose, pick one primary version and send the others to it. A store that answers on several addresses splits search signals across duplicate URLs and can leave the wrong version indexed, so settle the www or non-www question before you start sharing links. A sensible rule for creators:
| Situation | Good choice | Why |
|---|---|---|
| The storefront is your whole business | Root domain, www redirects to it | Shortest address for print and audio |
| You already have a website at the root | shop. or courses. subdomain | Nothing on the existing site is touched |
| You run several programmes | One subdomain per programme, or one for the storefront | Clear addresses, easy to remember |
| You sell mainly through a podcast or YouTube | Short subdomain such as learn. | Easy to say out loud |
A short, spellable address beats a clever one. If you would need to say "with two Ls and a hyphen" on a podcast, choose another name.
The DNS records you will actually use
You do not need to learn DNS. You need to recognise four record types.
| Record | What it does | Where you use it |
|---|---|---|
| A | Points a name to an IPv4 address | Root domain |
| AAAA | Points a name to an IPv6 address | Only if your host provides one |
| CNAME | Says one name is an alias of another name | www and other subdomains |
| ALIAS or ANAME | Acts like a CNAME at the root | Root domain, when the host gives a hostname instead of an IP |
The rule that trips people up is that a root domain needs an A record pointing to the host's IPv4 address, or an ALIAS if the host gives a hostname, because a CNAME cannot sit at the apex. The reason is technical: the root already carries SOA and NS records, and a name with a CNAME cannot have other record types, a restriction set out in RFC 1034 as explained in a DNS primer. Some DNS providers work around it with ALIAS records or CNAME flattening, so if your registrar offers one of these, use it when your storefront host gives you a hostname for the root.
For www or any other subdomain, a CNAME is usually enough. You add the subdomain part only (for example shop) as the host, and the value your storefront host gave you as the target.
Your storefront host will state the exact values. Copy them without retyping, and do not use values from a guide written for another platform: an IP address or hostname that works for one service will point your domain at the wrong place for another.
Connecting the domain, step by step
The screens differ between platforms and registrars, but the sequence is the same.

1. Add the domain in your storefront settings
Open the storefront's domain or address settings and enter the domain exactly as you want buyers to see it, for example shop.yourname.com. The platform then shows the records it expects, or a verification code. Keep that page open.
Where it goes wrong: entering the domain with https:// in front, or with a trailing slash. Enter the bare name.
2. Log in to your registrar and open the DNS panel
Find the section called DNS, DNS records or Zone editor. If your nameservers point to a separate provider, such as a DNS or CDN service, edit the records there, not at the registrar. Changes made in the wrong place do nothing, and this is the most common reason a correct-looking setup never works.
3. Remove or edit conflicting records
For the name you are connecting, look for existing A, AAAA, CNAME or ALIAS records. Only one record should point that name to the storefront. A leftover record that points somewhere else is a top cause of failures: troubleshooting guides list a conflicting A or ALIAS record on the same host among the first things to check. Leave MX records (email) and TXT records (email authentication) alone unless the instructions say otherwise.
4. Add the new records
For a subdomain: add a CNAME with the host set to the subdomain part only (shop) and the value set to the target your platform provided. For the root: add an A record with the host @ and the IP address given, or an ALIAS record if you were given a hostname. For www, add a CNAME as well and let the platform redirect one version to the other.
The common typing errors are worth knowing in advance: the record added to the wrong host (@ for the root, just the subdomain part for subdomains), a stray trailing dot, and a pasted value with a space on the end. Documentation for another site builder lists typos and trailing dots among the first things to remove when a connection fails.
5. Save, then verify in the storefront settings
Save the record, return to the storefront settings and press the verify or check button. If it says not yet, wait and try again rather than changing the records again. Each edit restarts your waiting.
6. Set the primary version and the redirect
Once verified, mark one version as primary. Anyone who types the other version, or an older platform address, should land on the primary one. Do this before you publish links anywhere.
How long it takes, and how to check it
DNS changes spread across the internet's resolvers at different speeds. One platform's guide says changes can take up to 48 hours to fully propagate, but most take effect within one to four hours. A propagation tool's documentation puts the range at a few minutes up to 48 hours, depending on the record's TTL. TTL (time to live) is the number of seconds a resolver may keep an old answer before asking again. If your registrar lets you edit it, lowering it to 300 seconds at least 24 hours before a planned change speeds up the switch, which is worth doing if you are moving a domain that already has visitors.
There is a reason the answer can differ between you and a friend in another city: ISP resolvers may impose their own TTL minimums, and geo-distributed setups can serve different answers by region by design. If it works on your phone's mobile data but not on your Wi-Fi, that is probably the cache, not your records.
To check progress without guessing, you can query several public resolvers, such as Google's 8.8.8.8 or Cloudflare's 1.1.1.1, and confirm they all return the same answer. A global checker such as dnschecker.org shows many locations at once. The same guide also suggests the dig +trace command if you are comfortable in a terminal and want to see the whole resolution chain.
The launch check
Once the platform shows the domain as connected, test it as a buyer would. Help documentation recommends opening both the plain and the www version in mobile and desktop browsers and in a private window, confirming that forms and links work, that HTTPS shows no certificate warnings, and that one version redirects to the preferred one. For a creator that means:
- Open the storefront home page and one product page on the new address.
- Check the padlock and that there is no warning about the certificate.
- Type the old platform address and the other version of the domain. Both should end up on the primary address.
- Go through a checkout to the payment step on a phone. Payment pages are where a mixed or broken address does most damage.
- Send yourself a link in an email and open it from there, so you see what a subscriber sees.
HTTPS matters beyond appearances. A launch checklist from one platform's support team calls SSL non-negotiable because payment processors require it and search engines factor it into rankings. Most hosts issue the certificate automatically after your DNS records resolve, so a missing padlock in the first hour usually means the records have not propagated yet.
When verification fails
Work through these in order. They cover nearly every case.
- It has not propagated yet. Wait 15 to 30 minutes and refresh before you touch anything. If an hour has passed, move on.
- The record is on the wrong host. For the root, the host is
@. For a subdomain, it is only the subdomain part. A record created asshop.yourname.com.yourname.comis a classic. - Two records fight. Delete any older A or ALIAS record on the same name that points elsewhere. Only one should point to your storefront.
- A proxy is switched on. If your DNS runs through a CDN service with an orange-cloud proxy, set the record to DNS only while the platform verifies it. Both troubleshooting guides mention this as a frequent blocker.
- A CAA record blocks the certificate. CAA records list which certificate authorities may issue certificates for your domain. If one exists and does not include your host's authority, the padlock never appears. Add the authority the host names or remove the restrictive record.
- A typo. Compare the value character by character with what the platform gave you, and remove trailing dots or spaces.
If you have worked through the list and the page still fails, contact your storefront host's support with a screenshot of your DNS records and the exact error. It gives them what they need in one message.
Practical rules that save creators trouble
Register the domain in your own name. Use an account you control, with your own email and two-factor authentication. A domain held by a freelancer is a business risk.
Turn on auto-renewal. A lapsed domain takes your storefront, your links and often your email offline at once. Calendar the renewal date as well.
Keep email in mind. If you use the domain for email as well, keep the MX and TXT records untouched when you edit the storefront records. Add the storefront records only on the specific host you are connecting.
Do not change records mid-launch. Connect the domain a week before a promotion, not the morning of it. Propagation delays and certificate issues are easier to fix when no one is waiting.
Plan your promotion on the new address. Once the address is stable, it becomes the base for everything you send. Our guide to digital storefronts that sell e-books and courses worldwide explains how the storefront, checkout and delivery fit together, and the guide on white label course platforms covers how to present a school as fully your own brand. For launches, discount codes and preorders work best when buyers see a consistent branded address from the ad to the checkout.
Our view: your address belongs to your brand, and the platform should not cost you while you build it
Creators build audiences with their name, their voice and their address. We think the tools underneath should make that easier, not tax the early stage of a business.
That is why BibliOWLteca is built around storefronts you can customise for your own educational brand, and around a model with no monthly fee: our claim is that you pay when you earn, with a transaction fee on completed sales rather than a subscription you carry through quiet months. For someone who is still testing a first e-book or a first course, that changes the maths of launching.
We built the platform specifically for educational content: e-books, courses with video and quizzes, templates, mentorship spaces and communities, with global payments in several currencies, including Pix, SEPA, crypto and Klarna, instant digital delivery, and European tax compliance. A branded address is the natural finishing touch to that: the first thing a new buyer sees, and the thing you will keep printing in slides, books and show notes for years.
Our advice is to settle your name and address early, keep them simple, and put your energy into the product and the audience behind it.
BibliOWLteca
Build your branded storefront with BibliOWLteca
BibliOWLteca is a marketplace and creator platform for selling e-books, courses, templates, mentorship programmes and other digital products. You get a customisable storefront, course hosting with video and quizzes, community features, analytics and secure digital delivery, with payments accepted in multiple currencies. We charge no monthly fee: the transaction fee starts from €0.99 per sale, and you can read the details on the pricing page.

If you are building a school for an international audience, including sellers expanding from Brazil into Europe, the localised checkout and payment options are designed to keep the buyer's journey simple. You can see the kinds of products creators publish in our categories, or start from the BibliOWLteca home page.
FAQ
Do I need a custom domain to sell online courses or e-books?
No, but it is the strongest signal of a real brand. A domain you own makes your address easier to remember and keeps search visibility and link reputation under your control. It is worth setting up before you invest in ads, print or podcast sponsorships.
Should I use the root domain or a subdomain for my storefront?
Use the root domain if the storefront is your whole business. Use a subdomain such as shop. or courses. if you already have a website at the root, because it leaves that site untouched. Whichever you choose, redirect the other version to it so you do not split your search signals across duplicate addresses.
How long does a custom domain take to start working?
Most changes show within a few hours, and a full spread can take up to 48 hours. The exact time depends on the record's TTL and on the caches your visitors' internet providers keep. If nothing works after a few hours, check for conflicting records and for records added to the wrong host.
Why does my domain show a certificate warning?
The certificate is normally issued automatically once your DNS records resolve to the host, so a warning in the first hours usually means propagation has not finished. If it persists, look for a CAA record that blocks the issuing authority, or a proxy that is switched on at your DNS provider.
Will connecting a domain break my email?
Not if you only add the storefront's A, ALIAS or CNAME records on the specific host you are connecting. Email depends on MX and TXT records, so leave those as they are, and take a screenshot of your DNS records before you change anything.
Sources
- Connect a Custom Address to Your Website, Fieldified Help
- Common DNS Records, DNSimple Help
- Setting Up DNS So a Website Resolves on the Internet, learndns.org
- Shopify DNS Settings: How to Configure DNS Records, firstpier.com
- Free DNS Propagation Checker, EdgeDNS
- DNS Records: Every Type, Nameservers and Propagation, ThatMy
- Shopify Store Launch Checklist, NextSky Support
- Troubleshooting DNS, Leadform Help
- Connect a Custom Domain to Your Website, Lindo.ai Docs
- Discount Codes for Your Dojo: Merch, Preorders and Stock
