Custom Domain for Your Link in Bio: A Plain Guide

Putting your link in bio on a custom domain (like links.yourname.com instead of a tool's address) makes it look like yours, keeps working if you ever switch tools, and fits neatly on a business card. The setup is a few DNS records, but DNS has a reputation for being confusing. This guide explains the parts in plain language: subdomain vs root domain, what a CNAME is, how SSL fits in, and what to click at a typical registrar.

Subdomain or root domain?

You have two choices for where your page lives.

A subdomain: links.yourdomain.com

A subdomain is anything in front of your main domain: links., me., hi., go.. This is the easiest and most common option because:

• it uses a standard CNAME record, which every DNS provider supports
• your main site at yourdomain.com stays untouched
• you can set it up in a few minutes

If you already have a website, use a subdomain.

The root domain: yourdomain.com

The root (also called the apex or naked domain) is the domain with nothing in front. Using it for your link in bio makes sense if you bought a domain just for this, like yourname.com, and do not have another site there.

The catch: the DNS standard does not allow a plain CNAME record at the root, because the root also has to hold other records like MX for email. Many DNS providers work around this with a feature called CNAME flattening, or with record types named ALIAS or ANAME. They behave like a CNAME at the root. If your provider offers one of those, a root domain works fine. If not, you may need to move your DNS to a provider that does, or use a subdomain.

What a CNAME record actually does

A CNAME says "this name is an alias for that other name". When someone visits links.yourdomain.com, their browser asks DNS where it lives, and DNS answers "go ask over there", pointing at your link-in-bio provider. The provider then serves your page.

A CNAME record has three parts:

• Type: CNAME
• Name (sometimes called Host): the subdomain, such as links
• Value (sometimes Target or Points to): the address your provider gives you

There is also a TTL (time to live), which controls how long DNS answers are cached. The default is fine.

Some providers also ask for a TXT record. TXT records do not route traffic; they hold a short piece of text that proves you control the domain, or that lets a certificate authority confirm it before issuing SSL.

How SSL works on a custom domain

SSL (really TLS) is what puts the padlock in the browser and the https:// in the address. Without it, browsers show warnings and many social apps will refuse to open the link.

You should not have to buy a certificate. Most modern hosts issue one automatically once your DNS points at them, and renew it before it expires. The usual sequence is:

1. You add the CNAME (and any TXT records the provider shows).
2. The provider sees your domain pointing at it.
3. A certificate is issued, often within minutes.
4. Your page loads over https.

If the padlock does not appear after an hour or so, the DNS records are usually the cause. Double-check them before anything else.

Steps at a typical registrar

Every registrar labels things slightly differently, but the flow is the same:

1. Log in where your domain's DNS is managed. This is usually your registrar, unless you moved DNS elsewhere (for example to Cloudflare).
2. Find the DNS settings for the domain. Look for "DNS", "Manage DNS", "Advanced DNS" or "DNS records".
3. Add a record. Choose CNAME.
4. In Name or Host, type only the subdomain part, like links. Most registrars add the rest for you. If you type links.yourdomain.com, some will turn it into links.yourdomain.com.yourdomain.com.
5. In Value or Target, paste the address your provider gave you.
6. Save. Add any TXT records the same way if asked.

Common gotchas:

• An existing record with the same name. You cannot have a CNAME and another record (like an A record) on the same name. Delete the old one first.
• A trailing dot. Some providers want the target to end with a dot, some add it for you. Follow what the form expects.
• Waiting. DNS changes often show up in minutes but can take longer. Give it time before changing things again.
• Root domains. If you are using the root, look for CNAME flattening, ALIAS or ANAME, as described above.

Will it affect my email or main site?

Not if you use a subdomain. A CNAME on links.yourdomain.com only changes where that one name points. Your website at yourdomain.com and your email (which depends on MX records) carry on as before.

With a root domain it needs more care. Do not delete MX or TXT records that handle your email when you add the flattened CNAME or ALIAS record. If you are unsure, use a subdomain.

Checking that it worked

You can check DNS from your terminal:

• dig links.yourdomain.com CNAME on macOS or Linux
• nslookup -type=CNAME links.yourdomain.com on Windows

If the answer shows your provider's address, DNS is done and you are waiting on SSL.

Custom domains on makerhandle

makerhandle Pro ($20 a year) supports a custom domain, either a subdomain like links.yourdomain.com or a root domain. The editor shows the exact records to add, checks them for you, and SSL is issued and renewed automatically. Read more on the custom domain page, compare plans on pricing, or see why it matters for solopreneurs.