Back to field notes
VOL. 05 · CUSTOM DOMAINS

Your brand, your hostname

How DNS verification works in LinkLane, and how to ship a lane that resolves on go.brand.com instead of linklane.io.

Guide5 min23 Apr 2026VOLUME 05 OF 08

Custom domains let an Enterprise account serve short links on its own hostname — go.brand.com/spring instead of linklane.io/spring. Verification is a one-time DNS TXT record handshake, and the per-link domain selector lives in the same panel as everything else.

Claiming a domain

  1. 1Visit /domains and submit go.brand.com.
  2. 2LinkLane returns a token like linklane-verify=…. Add it as a TXT record on the apex of the subdomain.
  3. 3Click Verify. LinkLane queries Google DNS-over-HTTPS, confirms the token, and marks the domain verified.
  4. 4Point the subdomain's A/AAAA (or CNAME) at LinkLane's edge using the instructions on the domain detail page.

Per-link domain swap

Once a domain is verified, every link's edit modal gains a domain dropdown. Pick a domain and the link's short_url switches host immediately — same code, same analytics, different brand surface. Unselect to fall back to the default linklane.io host.

Resolution under the hood

When a visitor hits go.brand.com/spring, the SPA's catch-all Redirector calls GET /api/preview/{code}?host=go.brand.com. The server confirms the link's configured domain matches the host before returning a destination, so codes scoped to one brand can't be hijacked under another.

Plan gating

Custom domains are Enterprise-only. The /domains navigation entry only renders for Enterprise users (or admins); other plans see an upsell card if they navigate to it directly.

NEXT UP
Guide

Shorten a hundred lanes in one paste

Bulk shorten, CSV import, CSV export, bulk tagging, bulk delete. The dashboard's power-user surface, explained.

READY?

Stop reading. Start shortening.