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

A custom short domain is a short, branded domain you own — like go.yourcompany.com or lnk.yourbrand.io — that replaces the generic slug from a third-party shortener in every link you publish. Setting one up takes less than 30 minutes, requires no server knowledge, and immediately makes every shortened URL you create reinforce your brand rather than someone else's.

This guide walks you through the full process: picking the right domain, understanding which DNS records to create, verifying the configuration, and going live — with troubleshooting tips for the most common snags.

---

Why a Custom Short Domain Matters

Before getting into the technical steps, it is worth understanding what you are actually buying with this effort.

Trust and click-through rates. When a recipient sees go.acme.com/summer-sale, they immediately know who sent it. Industry studies consistently show that branded, recognizable links earn meaningfully higher click-through rates than opaque bit.ly or tinyurl slugs, particularly in email and SMS channels where recipients are already skeptical of unknown links.

Brand consistency. Every link you share is a micro-impression of your brand. A branded short link turns a functional redirect into a branded asset that appears in social previews, analytics dashboards, presentations, and physical print.

Analytics ownership. When you control the domain, the click data is yours. You are not dependent on a third-party shortener's dashboard; you can integrate with your own systems and never lose historical data if a service shuts down.

Malware safety signals. Branded domains build a consistent reputation with email filters and browsers. Generic shorteners are frequently abused by spammers, which means links on those domains face blanket suspicion from security tools.

---

Step 1 — Choose the Right Domain for Link Shortening

A good short domain has three characteristics: it is short, it is recognizable, and it is available.

Length

Aim for 10–15 characters total including the TLD. Every character you trim from your short domain adds back to the available space for descriptive slugs.

Common patterns: - Full brand abbreviation + TLD: acme.io, zara.co - Subdomain of main domain: go.acme.com, lnk.acme.com, links.acme.com - Portmanteau or short variant: acm.ly, acmelnks.co

Using a subdomain of your existing domain (go.yourdomain.com) is usually the fastest path. You already own the parent domain, so there is no registration cost, and you benefit from the domain's existing reputation with email providers and browsers.

TLD choices

.com remains the most trusted TLD globally. After that, .co, .io, and .link are commonly used for branded shorteners. Country-code TLDs (.ly, .gg, .to) can look clever but may face blocks in certain regions or corporate firewalls — check your audience's geography before committing.

Registrar

If you need a new domain, register it at a reputable registrar: - Cloudflare Registrar — at-cost pricing, excellent DNS UI - Namecheap, Google Domains (now Squarespace), or GoDaddy all work fine

Once registered, you manage DNS either through the registrar's own nameservers or by pointing to a DNS provider like Cloudflare.

---

Step 2 — Understand the DNS Records You Will Need

DNS is the system that translates a domain name into an IP address (or another domain). For a custom short domain, you will typically create one of two record types.

CNAME record (most common)

A CNAME (Canonical Name) record maps your custom domain to the link-management platform's hostname. When someone visits your short link, DNS resolves your domain to the platform's servers, which handle the redirect.

Type:  CNAME
Host:  go          (or @ for a root/apex domain)
Value: links.go.fewly.tech   (example target — use your platform's specified value)
TTL:   3600

This is the most common setup when you use a subdomain (go.yourdomain.com). The Host field is just the subdomain prefix — so for go.yourdomain.com, enter go.

A record (for apex domains)

If you want the root domain itself (yourdomain.com, not a subdomain) to be your short domain, you cannot use a CNAME at the apex — the DNS specification does not allow it. Instead, you must point an A record to an IP address provided by your link platform, or use a DNS provider that supports CNAME flattening (Cloudflare calls this "CNAME at root").

Type:  A
Host:  @
Value: 203.0.113.45   (the IP provided by your platform)
TTL:   3600

TXT record (for domain verification)

Many platforms require you to add a TXT record to prove you own the domain before they activate it. This is a simple key-value string:

Type:  TXT
Host:  @   (or a specified subdomain like _fewly-verification)
Value: fewly-verify=a1b2c3d4e5f6   (the code your platform gives you)
TTL:   300

---

Step 3 — Configure DNS at Your Registrar or DNS Provider

The exact UI varies by registrar, but the process follows the same pattern everywhere.

Cloudflare (recommended)

1. Log in to dash.cloudflare.com and select your domain.
2. Click DNS in the left sidebar.
3. Click Add record.
4. Set Type to CNAME.
5. In Name, enter your subdomain prefix (e.g., go).
6. In Target, enter the hostname your link platform provided (e.g., links.go.fewly.tech).
7. Set the Proxy status toggle. For link shorteners, you generally want DNS only (the grey cloud) unless your platform explicitly supports Cloudflare proxying. Proxied records route traffic through Cloudflare's CDN and can interfere with SSL certificate issuance on the platform side.
8. TTL can stay at Auto.
9. Click Save.

If a TXT verification record is required, repeat the same process with Type: TXT, using the host and value your platform specifies.

Namecheap

1. Go to Domain List, click Manage next to your domain.
2. Select the Advanced DNS tab.
3. Click Add New Record.
4. Choose CNAME Record from the dropdown.
5. Enter your subdomain prefix in Host and the platform's target hostname in Value.
6. Set TTL to Automatic or 3600.
7. Click the green checkmark to save.

GoDaddy

1. Open My Products, click DNS next to your domain.
2. Under the DNS Records section, click Add.
3. Choose CNAME from the type dropdown.
4. Fill in Name (your subdomain) and Value (the target hostname).
5. Set TTL to 1 hour (3600 seconds).
6. Click Save.

General tips for any registrar

• Delete any existing conflicting records on the same host before adding new ones. If there is already an A record for go.yourdomain.com, remove it first or the CNAME will not work correctly.
• DNS propagation takes anywhere from a few minutes to 48 hours, though most modern DNS infrastructure propagates within 15–30 minutes. You can check propagation progress at dnschecker.org.
• Lower your TTL to 300 (5 minutes) before making changes so that corrections propagate quickly if something goes wrong. Raise it back to 3600 after everything is confirmed working.

---

Step 4 — Add Your Custom Short Domain in fewly

Once DNS is configured, the next step is connecting the domain to your fewly account.

1. Log in to fewly and navigate to Settings > Custom Domains (or visit the domain configuration docs for the exact menu path in your plan).
2. Click Add domain and enter your full short domain (e.g., go.yourdomain.com).
3. fewly will display the CNAME target and any TXT verification string you need to add to DNS. If you have not done this yet, do it now and wait for propagation.
4. Click Verify domain. The platform pings your DNS and confirms the records resolve correctly.
5. SSL is provisioned automatically once verification passes — typically within a minute or two using Let's Encrypt. You do not need to upload a certificate.

After verification, every new link you create in fewly can use your custom short domain as the base URL instead of the default fewly domain.

---

Step 5 — Test Your Setup End to End

Before promoting your new short domain publicly, run a manual end-to-end test.

Create a test link. In fewly, shorten any URL using your newly verified custom domain. You should get back something like go.yourdomain.com/test123.

Check DNS resolution.

dig CNAME go.yourdomain.com

The output should show your CNAME pointing to the platform's hostname with a short TTL.

Test the redirect. Open the short link in a browser. Confirm it redirects to the correct destination. Check that the browser address bar shows https:// — the SSL certificate should already be active.

Test from a mobile device on a different network (not your office WiFi) to rule out local DNS caching giving you a false positive.

Check link analytics. Visit your link analytics dashboard and confirm the test click was recorded. This verifies the full pipeline: DNS resolves → redirect fires → analytics event is logged.

---

Common DNS Problems and How to Fix Them

"Domain not verified" after 30 minutes

The most common cause is a typo in the CNAME target. Open your registrar's DNS panel and copy-paste the target hostname from your fewly dashboard rather than typing it manually. Also confirm there is no trailing period issue — some registrars require the trailing dot in FQDN values, others add it automatically.

SSL certificate not provisioning

This almost always means Cloudflare's proxy (the orange cloud) is turned on when it should be off, or the CNAME points to the platform host but the platform cannot verify domain ownership because TXT records are missing. Disable proxying and confirm TXT records are present.

Redirect loop

If you see a redirect loop error, the likely culprit is forcing HTTPS at the registrar or Cloudflare level while the platform is also trying to redirect to HTTPS. Turn off "Always Use HTTPS" or "Redirect to HTTPS" rules in Cloudflare if your link platform handles HTTPS itself.

Old links still using the default domain

Links already created before you added your custom domain will not retroactively change their base URL. You can recreate them using the new domain, or use fewly's bulk editing tools to update them in the link management dashboard.

---

Choosing Between a Subdomain and a Root Domain

Factor	Subdomain (go.brand.com)	Root domain (brand.co)
DNS record type	CNAME (simple)	A record or CNAME flattening
Registration cost	Free (you own parent)	New domain registration
Brand clarity	High — "go.brand.com" signals it is branded	Highest — all one entity
Setup complexity	Low	Medium
Email conflict risk	None	Must keep MX records separate
Recommended for	Most teams	High-volume link publishers

For the majority of businesses, a subdomain of your existing domain is the pragmatic choice. It is free, faster to set up, and carries the trust reputation of your main domain.

---

Maintaining Your Custom Short Domain

A custom short domain is not set-and-forget. Build these habits:

• Monitor DNS uptime. Any accidental deletion of your CNAME record will break every link you have ever published under that domain. Set up a free uptime monitor (UptimeRobot works well) pointing at one of your short links.
• Renew your domain before it expires. Enable auto-renew on your registrar account. An expired short domain is a catastrophic brand failure — all links go dead simultaneously.
• Audit your link portfolio periodically. As you grow, old campaign links may point to retired landing pages. Use the link management dashboard to update or archive stale links.
• Review click data. The analytics on a branded short domain are yours. Check them regularly through link analytics to understand which channels and campaigns drive the most engaged traffic.

---

Frequently asked questions

How long does DNS propagation take for a custom short domain?

Most DNS changes propagate within 15–30 minutes on modern infrastructure, though the formal maximum is 48 hours depending on TTL settings and resolver caching. Lowering your TTL to 300 before making changes speeds this up significantly.

Can I use the same custom short domain on multiple platforms?

No. A CNAME record can only point to one target at a time. You would need to pick one platform to handle the domain, or use separate subdomains for each platform (e.g., go.brand.com for one tool, lnk.brand.com for another).

Do I need to buy a new domain for a custom short domain?

Not necessarily. The most cost-effective approach is to create a subdomain of a domain you already own (go.yourdomain.com). You only need to register a new domain if you want a root-level short domain that is entirely separate from your main website domain.

Will changing my short domain break existing links?

Yes. Links are tied to the domain they were created under. If you change your custom short domain, old links will stop resolving. Plan domain changes carefully, and use redirects at the DNS or web server level to forward traffic from the old domain to the new one during any transition period.

Is an SSL certificate included, or do I need to set one up separately?

fewly provisions SSL automatically via Let's Encrypt once your domain verifies successfully. You do not need to purchase, upload, or renew a certificate manually. See the domain docs for details on the provisioning timeline.

---

Get Started with Your Custom Short Domain

Setting up a custom short domain is one of the highest-leverage moves for anyone who publishes links at scale. You get branded URLs, richer analytics, better deliverability, and a professional appearance — all for the effort of a few DNS record additions and a five-minute verification flow.

Ready to make every link you share work harder for your brand? Start free and connect your custom domain today — no credit card required on the free plan, and branded links are available from day one.