how-to-guides

How to Set Up a Custom Domain for Short Links (DNS Guide 2026)

Step-by-step guide to setting up a custom domain for short links. Covers registrar picks, CNAME setup on Cloudflare, Namecheap, and GoDaddy, and auto SSL.

Team U2L • 17 min read

Most people who search for "custom domain short links" have already decided they want branded URLs. What they're actually stuck on is the DNS bit. Where do you buy the domain? Which record goes where? What if your registrar is GoDaddy and everyone keeps mentioning CNAME flattening? Why is the browser still throwing a security warning ten minutes after you saved everything?

This guide answers all of that in order. It walks through the five real steps of standing up a branded short domain, then gives you the exact DNS clicks for Cloudflare, Namecheap, and GoDaddy. It also covers the two mistakes that eat up the most support tickets (apex domains and Cloudflare's orange cloud), plus how long you should actually wait before assuming something is broken.

By the end, you should be able to go from "I don't own a short domain yet" to "my links are live on mybrand.co/anything" in under an afternoon. Most of that afternoon is DNS propagation. The actual work takes about fifteen minutes.

To set up a custom domain for short links, register a short branded domain (like mybrand.co or go.mybrand.com), add it to your URL shortener's dashboard, then add one CNAME record at your DNS provider pointing your subdomain to the shortener's target. Verification and SSL are automatic once DNS resolves, which usually takes 5 to 30 minutes. Branded custom short links get an average 34% higher click-through rate than generic shortener URLs.

Table of Contents

A custom domain for short links is a domain you own (like mybrand.co or go.mybrand.com) that your URL shortener uses to build branded short URLs. Instead of a generic shortener URL, every link you create lives on your domain: mybrand.co/spring-sale instead of bit.ly/3xK9a2. The redirect still runs through the shortener's infrastructure, but the URL your audience sees is yours.

The mechanics are simpler than they sound. You buy a domain from any registrar. You point one DNS record at your shortener. The shortener handles the SSL certificate and the actual redirect. Every branded short link you make from that point forward gets served from your domain, with your slug, without your team touching DNS again.

The reason this matters at all is trust. Generic shortener domains are, at this point, load-bearing infrastructure for phishing. When someone sees an unfamiliar short link in an email, they hesitate. When they see your brand's domain instead, they click. That's the whole game. For more on this psychology, see what a branded link actually is and why it works.

Why Bother? The 34% CTR Story

Custom domains for short links exist because branded URLs consistently beat generic ones on click-through rate. Rebrandly's ongoing A/B testing puts the lift at around 34%. Some sources cite up to 39% or 40% depending on channel. The exact number moves around by study, but the direction never does: branded beats generic, everywhere.

Where does the lift come from? A few compounding effects:

Trust at a glance. Your audience already recognizes your domain. Seeing it in the URL removes the "what is this link?" hesitation.

Deliverability. Email providers and SMS carriers are noticeably harder on generic shortener domains because so much spam moves through them. A branded short domain lives on your own reputation, not on the aggregate reputation of bit.ly or tinyurl.com. Fewer emails get filtered out.

Ad platform trust scores. Google Ads and Meta Ads both use the shown URL as one signal for ad quality. Your own domain in the display URL usually scores higher than a shortener domain.

Ownership. If you ever switch shorteners, your domain moves with you. Every existing link keeps working the moment DNS points somewhere new. On a generic shortener, migrating means retiring every link you ever shared. That risk gets real once you've been sharing links for a few years.

Honestly, if you're doing any serious volume of links (email, ads, SMS, print, or QR code campaigns), the 34% number alone pays for the domain a hundred times over.

Pick Your Short Domain First

Before you touch DNS, pick the domain. A good short domain has three qualities: it's short, it reads like your brand, and it doesn't confuse anyone at a glance.

Aim for 4-8 characters on the second-level domain (the part before the TLD). Long domains defeat the point of shortening. strategygroupofficial.com/sale isn't a short link. strat.co/sale is.

Pick a TLD that reads like a link. The go-to options:

  • .co reads like .com and is widely available. Usually more expensive than .link but the most familiar to non-technical audiences.
  • .link is purpose-built for this exact use case. Very affordable, and the TLD itself signals "this is a link."
  • .io, .app, .gl, .ly all work and stay short. Availability is hit or miss.
  • .com is ideal but almost never available in short form.

Consider a subdomain first. You don't actually need to buy a new domain at all. If you already own mybrand.com, you can use go.mybrand.com or link.mybrand.com as your short domain. It's free (you already pay for the parent domain) and it reinforces the main brand more strongly than a separate .co or .link does. The trade-off is length, and that trade-off often doesn't matter for internal or email use.

Skip cheap-looking TLDs. .xyz, .info, .top, and similar TLDs get flagged as spam-adjacent by some email providers. You save two dollars a year and lose deliverability. Not a good trade.

For registrars, Namecheap, Porkbun, and Cloudflare Registrar are the standard picks. All three are cheap, technically competent, and don't try to upsell you domain privacy for $9/month. GoDaddy works, but expect to pay more and to fight with the interface a bit.

The 5-Step Custom Domain Setup

Step 1: Register your short domain

Go to your registrar of choice (Namecheap, Porkbun, Cloudflare Registrar, or GoDaddy) and search for the short domain you want. Buy it. Enable auto-renewal so you don't accidentally lose the domain and break every branded link you've ever shared. Enable WHOIS privacy if the registrar offers it for free (Namecheap and Cloudflare both do).

If you're using a subdomain of a domain you already own, skip this step entirely. Just decide on the subdomain (go.mybrand.com, link.mybrand.com, l.mybrand.com) and move on to Step 2.

Step 2: Add the domain in your URL shortener dashboard

Log in to your URL shortener. In U2L AI, that's the dashboard's Domains section. Enter the domain exactly as you want it to appear in your short links: mybrand.co if you're using the apex domain, go.mybrand.com if you're using a subdomain.

The shortener will immediately give you a CNAME target. Something like custom.u2l.ai or a similar hostname. Copy that value. You'll need it in Step 3.

Step 3: Add the CNAME record at your DNS provider

Go to your DNS provider (which may or may not be your registrar - if you use Cloudflare's nameservers, DNS lives at Cloudflare even if the domain is registered elsewhere).

Add a single CNAME record with these values:

  • Type: CNAME
  • Name: @ for an apex domain, or the subdomain part (go, link, l) for a subdomain
  • Value: the CNAME target from Step 2
  • TTL: Auto, or 3600 seconds if TTL is required

Save. That's the entire DNS side of the work.

Step 4: Wait for verification and SSL provisioning

Go back to your shortener dashboard and click Verify (or wait a few minutes if verification is automatic). The shortener resolves the CNAME, confirms it points to their infrastructure, and starts SSL certificate issuance. Certificates are issued by Let's Encrypt or a similar authority behind the scenes. This is automatic. You don't handle certificates.

Total time here is usually 5 to 30 minutes. It can be as fast as one minute or as slow as a few hours depending on how quickly DNS propagates through your provider and the resolvers in between.

Once the domain shows as verified with SSL active in the shortener dashboard, create a link. Pick a memorable slug: mybrand.co/launch, mybrand.co/hi, whatever fits. Click the link. Confirm it redirects to the destination and that the browser shows a green padlock (valid SSL).

If everything works, you're done. Every future short link you create can use the new domain from a dropdown next to the slug field.

DNS Setup on Cloudflare, Namecheap, and GoDaddy

The exact clicks depend on your DNS provider. Here's what to do in each.

Cloudflare

Cloudflare is the smoothest option and it's what we recommend if you don't already have a strong preference. Log in, select your domain, and go to DNS → Records.

Click Add record. Set Type to CNAME, Name to your subdomain (or @ for apex), and Target to the CNAME value your shortener gave you. Set Proxy status to DNS only by clicking the orange cloud until it turns grey. This is the single most-missed step in the entire process. If the cloud stays orange, Cloudflare proxies the traffic instead of resolving through, and the shortener never sees a matching CNAME to verify.

Save. Cloudflare's DNS resolves in under a minute globally. SSL provisioning typically happens right after.

One bonus: Cloudflare supports CNAME flattening automatically, which means you can use a CNAME record on the apex (@) of your domain. Most other providers don't support this and force you to use a subdomain if you want a CNAME. If apex-level short links matter to you, this alone is worth moving your DNS to Cloudflare.

Namecheap

If your domain is registered with Namecheap and you're using their default DNS, log in and go to Domain List → Manage → Advanced DNS.

Click Add New Record. Choose CNAME Record, set Host to your subdomain (go, link, l), and set Value to the CNAME target from your shortener. Leave TTL as Automatic. Save.

Namecheap does not support CNAME on the apex domain. If you want to use mybrand.co (no subdomain) with Namecheap DNS, you need to switch to Cloudflare's nameservers first. This is straightforward: create a free Cloudflare account, add your domain, follow the nameserver change instructions on Cloudflare, then update Namecheap's nameservers to point at Cloudflare's. Once that's done, use the Cloudflare steps above.

For subdomain setups, Namecheap's default DNS works fine.

GoDaddy

GoDaddy is the most annoying of the three. Log in, go to My Products → DNS, and click Add to create a new record.

Choose CNAME, set Name to your subdomain (or @ for apex), and set Value to your shortener's CNAME target. Save.

The catch: GoDaddy does not support CNAME flattening. If you want to use your apex domain (no subdomain) for short links, you cannot do it with GoDaddy DNS. Either use a subdomain (go.mybrand.com), or move DNS to Cloudflare while keeping the registration at GoDaddy. Moving DNS is a nameserver change; the domain stays where you bought it.

For subdomains, GoDaddy DNS is fine, if a bit slow to update.

Apex Domain vs Subdomain: Which Should You Use?

The apex domain is the bare version - mybrand.co. The subdomain is anything before it - go.mybrand.co, link.mybrand.co.

Apex domains look cleaner. mybrand.co/sale is objectively shorter and more brand-forward than go.mybrand.co/sale. This matters if you're printing short links on business cards or reading them aloud on a podcast.

The trade-off: not every DNS provider supports CNAME on the apex. You need CNAME flattening (Cloudflare calls it "CNAME flattening," AWS Route 53 calls it ALIAS, some call it ANAME). If your DNS provider doesn't support it, you can either move DNS to one that does, or use a subdomain instead.

Subdomains work everywhere. Standard CNAME records on subdomains are supported by every DNS provider that exists. go.mybrand.com or l.mybrand.com reads perfectly well in most contexts, and you don't have to touch nameservers.

Our take: if you already have DNS on Cloudflare, use the apex. If not, use a subdomain and move on with your day. The CTR difference between mybrand.co/x and go.mybrand.co/x is negligible.

Common Setup Mistakes That Break Everything

A few things that trip up almost everyone.

Cloudflare's orange cloud is on. If you're using Cloudflare DNS and the proxy is enabled (orange cloud instead of grey), the shortener can't verify your CNAME. Turn the cloud grey. This is the #1 support ticket.

You added the CNAME target as a URL, not a hostname. CNAME records take a hostname (custom.u2l.ai), not a full URL (https://custom.u2l.ai/). If you paste a URL, the record won't resolve.

You tried to add A records instead. For most shortener setups, you want CNAME, not A. A records point at a fixed IP address, which shorteners intentionally avoid because their edge infrastructure changes IP addresses regularly. CNAME lets them route around infrastructure changes without breaking your links.

You're checking too fast. DNS propagates in stages. Your local resolver might still be cached. Give it 15 minutes minimum before assuming something is wrong. Use a tool like DNS Checker to see propagation across regions.

You bought a .tk or .ml domain to save money. These are widely used for spam and phishing. Email providers and browsers treat them harshly. Spend the extra $5 a year on .co or .link.

The registrar's DNS is different from where you thought it was. If you moved nameservers to Cloudflare years ago but forgot, adding a record at Namecheap or GoDaddy will have zero effect. Check nameservers first: dig ns mybrand.co will show which provider is actually authoritative.

How Long Setup Really Takes

The honest breakdown:

  • Registering a domain: 5 minutes.
  • Adding the domain to your shortener: 30 seconds.
  • Adding the CNAME record: 1 minute.
  • Waiting for DNS to propagate: 5 to 30 minutes typically. Occasionally up to a few hours. Very rarely 24-48 hours.
  • Waiting for SSL to provision: Usually 1-2 minutes after DNS resolves.
  • Testing your first link: 30 seconds.

Total active time: under 15 minutes. Total elapsed time: usually under an hour. Don't be alarmed if it takes longer the first time; DNS is genuinely unpredictable at the edges.

Once the domain is live, you never touch DNS again. Every future short link uses the domain from the dropdown, and creation takes as long as any other short link would. If you're managing links at scale, U2L AI's bulk import features let you upload thousands of branded short links from a CSV without touching them one by one. Custom domains, dynamic QR codes, and full analytics all live in the same dashboard, which keeps operations sane as you grow. For the wider view of what a modern shortener stack should include, our roundup of the best URL shorteners with custom domain support walks through pricing, feature depth, and setup polish for each major player.

Once branded links are live, most teams want to layer analytics and campaign tracking on top. The natural next steps are our complete guide to link tracking and how to use UTM parameters to track marketing campaigns. And if you're curious whether shortened URLs affect SEO (spoiler: 301 redirects pass almost all link equity), our URL shortener SEO breakdown is a good follow-up.

Frequently Asked Questions

Do I need a paid URL shortener plan to use a custom domain?

Yes, on almost every platform. Custom domains are a paid feature at Bitly, Rebrandly, Short.io, and U2L AI. The good news is entry-level paid plans that include custom domains are cheap - check u2l.ai/pricing for current U2L AI plans. A few free tiers (Cuttly, Rebrandly's free plan) include one custom domain but cap monthly link volume tightly.

How much does a short domain cost per year?

A .co domain typically runs $25-$35/year. A .link domain is often $4-$15/year. A .io or .app domain is somewhere in the middle. Subdomains of a domain you already own are free. Auto-renewal is a must-have; letting a branded domain expire is the fastest way to break every link you've ever shared.

Not directly on the apex - you don't want short links competing with your main site's URL structure. Use a subdomain instead: go.mybrand.com, link.mybrand.com, or a single-letter version like l.mybrand.com. It's free, it reinforces the main brand, and it doesn't interfere with anything on the main site.

Why does the shortener need a CNAME record specifically?

Because CNAME points a name to another name (like mybrand.co → custom.u2l.ai), not to a fixed IP address. Shorteners run on distributed edge networks where the underlying IPs change regularly. A CNAME lets them route around any infrastructure change without touching your DNS. If they used A records instead, every IP change would mean every customer editing their DNS.

What is CNAME flattening and do I need it?

CNAME flattening lets you use a CNAME record on the apex of your domain (mybrand.co with no subdomain), which technically the DNS spec doesn't allow. Cloudflare and AWS Route 53 support it transparently. Namecheap and GoDaddy don't. If you want to use your bare domain for short links, you need a DNS provider that supports CNAME flattening (or ALIAS/ANAME records). Otherwise, use a subdomain.

How long does DNS propagation actually take?

Usually 5 to 30 minutes. Sometimes up to a couple of hours. Rarely up to 48 hours, though this mostly happens when TTLs were set very high before the change. If you set TTL to Auto (or under 3600 seconds) before changing anything, propagation stays fast.

No. Adding a custom domain creates a new domain in your shortener account; it doesn't affect any existing links on the previous domain. Existing links keep working. Only new links you create with the custom domain live on that domain. If you want to migrate old links, most shorteners let you bulk-edit the domain field.

Can I have multiple custom domains on one account?

Yes. This is common for agencies managing multiple client brands, or businesses with distinct product lines. Higher-tier plans typically allow more custom domains - check the specific plan limits for whichever shortener you're using. U2L AI's Team plan supports a large number of custom domains for exactly this use case.

Custom domain short links take about fifteen minutes of active work and give you a lift on every campaign you run afterward. Register the domain, add it to your shortener, drop in one CNAME record, wait for DNS, ship your first branded link. The infrastructure side is boring on purpose. What you do with those links from here on is where the actual work starts.

Create your account on U2L AI and connect your first custom domain in the dashboard - the shortener, QR codes, and bio pages all use the same domain once it's set up.

Ready to try U2L AI?

Free forever plan. No credit card required.

Get Started Free View Pricing