← All posts

Tutorial4 min readThe Trizlink team

How to set up a custom domain for your short links

Add your own domain and prove you own it; serving links from it is not switched on. Here is what to add in DNS, what verification is actually checking, and what to do when it does not verify.

A custom domain is a hostname you own — usually a short subdomain such as go.example.com — that you add to Trizlink and prove you own with DNS records. Serving links from it is not switched on, so your short links still use the shared domain.

Choose the hostname first

Pick a subdomain rather than your apex domain. Using example.com itself means every short link shares a hostname with your website, which constrains both and makes a mistake in either far more expensive. A dedicated subdomain — go, link, l, or your brand — keeps the two independent. It is also the difference a shared shortener domain makes to whether your links survive a mail filter.

  • Short matters: the whole point is a compact URL, and every character of the hostname is spent before the slug starts.
  • Memorable matters more than clever. People retype these from screenshots and printed material.
  • Do not reuse a hostname that has served something else. Old links, caches and bookmarks will collide with your new ones.
  • Decide once. Changing the hostname later means every link already published now points at a name you no longer serve.

Add the DNS records

  1. In Trizlink, add the domain in the workspace’s domain settings. You are shown the exact records to create, generated for that hostname.
  2. In your DNS provider, create the CNAME record for the hostname, pointing at the target Trizlink shows you.
  3. Create the verification TXT record alongside it. This is what proves you control the name; without it a CNAME alone is not enough.
  4. Save, and come back to Trizlink to run the check.

Two things about the records are worth knowing in advance. Many DNS interfaces append the zone automatically, so entering "go.example.com" as the host can silently create go.example.com.example.com — enter just "go" if the provider shows the zone beside the field. And a CNAME cannot coexist with other records on the same name, which is another reason not to reuse a hostname.

What verification is checking

Verification is two questions, not one. Does the TXT record prove you control this hostname, and does the CNAME actually resolve to us? A domain can pass the first and fail the second — usually because the CNAME was created on the apex instead of the subdomain, or because a proxying setting is intercepting it.

Propagation is the usual reason a correct setup fails on the first attempt. DNS changes take effect on a schedule set by the record’s TTL, so a change made against a one-hour TTL can take up to that long to be visible everywhere. Re-running the check is safe and costs nothing; changing the records again while waiting is what turns a five-minute job into an afternoon.

When it does not verify

  1. Check the hostname for a doubled zone (go.example.com.example.com) — the single most common cause.
  2. Confirm the CNAME is on the subdomain, not the apex.
  3. If your DNS provider offers a proxy or CDN toggle on the record, turn it off for this hostname; a proxy answers instead of us.
  4. Look for a conflicting record on the same name — an old A record or an existing CNAME will win.
  5. Wait for the TTL and re-check before changing anything. Most "it is broken" reports are propagation.

What a custom domain actually buys

  • Reputation you control. Links on a shared domain inherit the behaviour of everyone else on it, and shared shortener domains do get blocked by mail filters and corporate networks. Your own hostname carries only your history.
  • Click-through. A recognisable domain in a link is the difference between "this is from them" and "this is from somewhere", particularly in email and in print.
  • Portability. Links served from a name you own would make a move of tools a DNS change rather than a broken archive; serving links from your own domain is not switched on.
  • Consistency across surfaces. A domain you own could carry your short links and your bio page alike; serving either from it is not switched on.

The reputation point is the one most often discovered too late. A link that works perfectly when you test it can still be stripped by a recipient’s mail filter, and the sender never finds out — the message simply performs badly for reasons that look like content.

After it verifies

Verifying the domain does not change where links serve: serving links from it is not switched on, so new links in that workspace still use the shared domain. Links you created earlier keep serving from the domain they were made on — deliberately, because rewriting a published link is the one thing a link platform must never do.

Bio pages are in the same position: you can add your own domain and prove you own it, but serving a link-in-bio page from it is not switched on.

Frequently asked

What is a custom domain for short links?

A hostname you own — usually a short subdomain like go.example.com — that you add to Trizlink and prove you own with DNS records. Serving links from it is not switched on.

Which plans include custom domains?

Pro includes one custom domain and Team includes five. The Free plan serves links from the shared domain.

Should I use a subdomain or my main domain?

A subdomain. Using the apex means your short links and your website share a hostname, which constrains both and makes any mistake in either far more expensive.

What DNS records do I need?

A CNAME on the chosen hostname pointing at the target Trizlink shows you, plus a TXT record that proves you control the name. Both are required — a CNAME alone does not verify.

How long does verification take?

Usually minutes, but it is bounded by your record’s TTL, so a change against a one-hour TTL can take that long to be visible everywhere. Re-running the check is free; changing the records again while waiting is what causes most delays.

Why is my domain not verifying?

Most often the hostname has a doubled zone because the provider appended it automatically, the CNAME is on the apex rather than the subdomain, a proxy or CDN toggle is intercepting the record, or an old conflicting record on the same name is winning.

Do my existing short links move to the new domain?

No, and deliberately so. Links already published keep serving from the domain they were created on; rewriting a link that is already in circulation is the one thing a link platform must never do.

Share this post

https://trizlink.com/blog/how-to-setup-custom-domains

Read next