A custom domain means your link pages live at an address you own — links.yourband.com — instead of at your tool’s address. It is the feature people most often assume requires a developer, and it is actually two DNS records and some waiting. This guide covers both halves: whether it is worth doing, and the small number of things that genuinely go wrong when you do.
What it actually changes
Recognition, first. A fan deciding whether to tap a link in a DM or a story sees the address before anything else, and yourband.com is a name they chose to follow; a link-tool domain is a name they have seen attached to a thousand strangers. The page on the other side is identical — the address is the part doing the reassuring.
Continuity, second, and this is the quieter and larger reason. Every campaign you run teaches fans, posters, and press kits an address. When that address is on a domain you own, the teaching accrues to you: if you ever change tools, the domain moves with you and can point wherever you go next. When it is on a tool’s domain, the accrual belongs to the tool. A custom domain is, among other things, an exit you set up in advance — the same logic as owning your email list, applied to your address.
What it does not do
A custom domain does not make pages rank in search, load faster, or convert more by itself — anyone selling it as a growth lever is selling. It also does not change what happens to your existing links: on DropRoute the old addresses keep serving forever alongside the new domain, so nothing already printed or pinned breaks the day you switch. The honest framing is that a custom domain is brand hygiene and long-term insurance, priced accordingly: it is part of the Artist plan, not an enterprise upsell, because it costs nearly nothing to provide.
The two records, in plain language
Two words do most of the intimidating here. A domain is the address you own and pay for yearly. DNS is the public directory that tells the internet where each of your names should go, and it lives at your registrar — GoDaddy, Namecheap, Cloudflare, wherever you bought the domain — not in your link tool. Connecting a domain means adding two entries to that directory.
The first is a TXT record: a small text note published under a name only you control, which proves to DropRoute that the domain is really yours — anyone can type links.yourband.com into a form; only the owner can publish a note under it. The second is a CNAME record, which points the name at DropRoute so visits arrive. Your tool shows you both values exactly; your job is to paste them into the registrar’s DNS page without improvisation. HTTPS needs no work from you at all — the certificate is issued automatically once ownership is proven, which retires the last genuinely technical step this process used to have.
One recommendation that prevents most trouble: use a subdomain (links.yourband.com), not the bare domain. Your bare domain probably already runs your website, and a subdomain leaves it completely untouched — the two coexist without negotiation.
The three mistakes that cause all the tears
- The doubled hostname. Many registrars append your domain to the Host field automatically, so typing the full name produces links.yourband.com.yourband.com — a name nobody is checking. If the form already shows your domain after the box, enter only the part in front.
- The orange cloud. On Cloudflare, a record set to "Proxied" answers with Cloudflare’s own addresses instead of yours, so verification can never see the record pointing where it should. The record that points at your link tool must be "DNS only" — the grey cloud.
- The lost verification value. The TXT value is shown once, at creation, and cannot be recovered afterwards — only a scrambled fingerprint of it is stored, on purpose. Copy it when it appears; if it is gone, disconnect the domain and add it again for a fresh one.
The waiting, and what the statuses mean
New DNS records take time to become visible everywhere — usually minutes, occasionally hours — and no amount of pressing the button changes that. What the button can do is tell the truth about now: DropRoute’s Check now re-reads your DNS fresh on each press and shows the raw records it can see, so a stalled setup is diagnosable rather than mysterious. The statuses read in order — waiting for DNS, ownership being verified, certificate being issued, active — and a domain serves fan traffic only when it is fully active with a certificate, never half-configured.
Nothing is at risk while you wait. Your DropRoute address keeps serving throughout, the connection can be abandoned and retried without consequence, and no live link is touched until the domain is actually working. The worst possible outcome of a botched DNS record is that nothing changes.
After it is live
New shares can use the new address; everything already in the world keeps working at the old one, so there is no cutover moment to fear and no evening of updating old posts. From then on the domain is checked automatically every day — if a record drifts months later, you are told by email rather than by a fan with a screenshot.
Two security details are worth understanding rather than being annoyed by. Adding or removing a domain asks for your password again even when you are signed in, because attaching a hostname to someone else’s account is precisely what a stolen session would try. And the daily re-check exists because DNS is editable by anyone with registrar access — the record proving your setup today does not prove it forever, so it is re-proven quietly instead of assumed.