Replace your default unil.ink/username URL with a domain you own — so your link-in-bio page lives at yourname.com instead of someone else's subdomain.
- Connect any domain you own to your UniLink page by adding a CNAME or A record at your DNS registrar.
- Use a subdomain (links.yourbrand.com) with a CNAME record — it's easier and works with every registrar.
- DNS changes take 15 minutes to 48 hours to propagate; SSL is issued automatically once UniLink verifies.
- Common blockers: CNAME on root domain, high TTL, conflicting A records — all fixable in minutes.
Every UniLink page works out of the box at unil.ink/username — that URL is live the moment you create your account. But for creators and businesses that take their brand seriously, sending people to someone else's domain undercuts the whole point of building a professional presence. A custom domain means your link-in-bio URL reads yourname.com or links.yourbrand.com, not a shared platform slug. It signals ownership, permanence, and credibility in a way that no amount of design polish on a third-party URL can replicate. The setup takes about ten minutes once you know what you're doing, and this article will walk you through every step — including the gotchas that catch people out.
What custom domains do
When you connect a custom domain to UniLink, visitors who type yourname.com (or whatever domain you choose) land on your UniLink page — the same page, same blocks, same design — but the URL in the browser bar shows your domain instead of unil.ink. This works because DNS records point your domain to UniLink's servers, and UniLink's infrastructure recognizes the domain, serves your page, and handles SSL so the connection is secure. From the visitor's perspective, they're on your domain. From UniLink's perspective, it's still your page.
The custom domain feature supports two connection methods. A CNAME record lets you point a subdomain — links.yourbrand.com, bio.yourname.com, or anything you choose — to UniLink's server hostname. An A record lets you point a root domain — yourbrand.com with no prefix — directly to UniLink's IP address. Most creators and businesses use a subdomain with a CNAME record because it's easier to configure, supported by every DNS registrar without exception, and faster to verify. Root domain connections via A record require a few extra steps and some registrars handle them differently, but they work fine once configured.
SSL is handled automatically. Once UniLink detects your DNS records are correctly pointing to its servers, it provisions a free certificate via Let's Encrypt, usually within a few minutes of successful verification. Your domain status in the Dashboard moves from "Pending" to "Active" once both DNS verification and SSL issuance are complete. You don't need to buy a certificate or configure anything on your end — UniLink handles it entirely.
How to add your domain
- Go to Domain settings: In your UniLink Dashboard, open Settings and navigate to the Domain section.
- Click "Add domain": Enter the full domain or subdomain you want to connect — for example,
links.yourbrand.comoryourname.com. Click Continue. - Choose your connection method: Select CNAME (recommended for subdomains) or A record (for root domains). UniLink will display the exact values to add.
- Copy the record values: UniLink shows you the Type, Name (host), and Value (target) for the DNS record. Copy these — you'll need them at your registrar.
- Open your DNS registrar: Log into Cloudflare, Namecheap, GoDaddy, Google Domains, Squarespace, or wherever you purchased the domain.
- Add the DNS record: Navigate to DNS management for your domain. Add a new record with the Type, Name, and Value UniLink provided. Set TTL to 300 (5 minutes) to speed up propagation during setup.
- Remove conflicting records: If there's an existing A record or CNAME for the same name (host), delete it first. Conflicting records cause verification to fail.
- Return to UniLink and click Verify: UniLink will check for the DNS record. If propagation is complete, status changes to Active. If not, wait and try again — propagation can take up to 48 hours.
How to configure each connection type
- CNAME for a subdomain (recommended): Set the record Type to CNAME, Name to your subdomain prefix (e.g.,
linksfor links.yourbrand.com — enter just the prefix, not the full domain), and Value to the UniLink server hostname shown in the Dashboard (e.g.,custom.unil.ink). Save the record. - A record for a root domain: Set the record Type to A, Name to
@(which represents the root domain at most registrars), and Value to the IP address UniLink provides. Some registrars label the Name field differently — use whatever represents the bare domain root. Save the record. - Verify TTL: Confirm TTL is set to 300 seconds (5 minutes) or similar low value during setup. A TTL of 3600 or higher means changes take up to an hour to propagate even after DNS correctly updates.
- Wait and check propagation: Use a tool like dnschecker.org to watch the record propagate across global DNS servers. Once you see green checkmarks in most regions, go back to UniLink and click Verify.
- Confirm SSL issuance: Once status shows Active in the Dashboard, open your domain in a browser and confirm the padlock appears in the address bar. If it shows a certificate warning, wait a few more minutes and refresh — SSL issuance runs after DNS verification completes.
Key settings and what they mean
| Setting / concept | What it is | What to do |
|---|---|---|
| CNAME record | Maps a subdomain to another hostname. Works on subdomains only. | Use this for links.yourdomain.com, bio.yourname.com, etc. Easiest method. |
| A record | Maps a domain or subdomain to an IP address. Required for root domains at most registrars. | Use this only if you want yourdomain.com (no prefix) to point to UniLink. |
| Record Name / Host | The subdomain prefix or root identifier in your DNS record. | For subdomains: enter just the prefix (e.g., "links"). For root: enter "@". |
| Record Value / Target | Where the DNS record points — a hostname (CNAME) or IP address (A record). | Copy exactly from the UniLink Dashboard. Don't add trailing dots or spaces. |
| TTL (Time to Live) | How long DNS servers cache the record before checking for updates. | Set to 300 during setup. After the domain is active, you can raise it to 3600. |
| Domain status: Pending | UniLink is waiting to detect your DNS record. | Normal state during propagation. Give it 15–30 minutes, then click Verify again. |
| Domain status: Active | DNS verified and SSL certificate issued. Domain is live. | You're done. Test the URL in a browser to confirm it resolves correctly. |
| CAA records | Optional DNS records that restrict which certificate authorities can issue SSL for your domain. | If you have CAA records, add an entry allowing Let's Encrypt (letsencrypt.org). |
How to get the most from custom domains
The single biggest mistake people make after connecting a custom domain is not updating their social bios and marketing materials to reflect it. Your new URL doesn't promote itself. Once your domain is Active in UniLink, update the link in your Instagram bio, TikTok bio, Twitter/X bio, email signature, YouTube channel description, and any other places where you currently link to your unil.ink/username URL. The whole point of having a branded domain is getting it in front of people — don't let your old URL continue getting the traffic.
Think about the subdomain you choose before you set it up, because changing it later means going through the DNS process again. Common choices are links.yourdomain.com, bio.yourname.com, or go.yourbrand.com — short, readable, and clearly associated with your main domain. Avoid long or clever subdomains that are harder to remember or type. If you have a personal brand, bio.yourname.com reads well. If you're a business, links.yourbrand.com or connect.yourbrand.com work better than something abstract.
If you own multiple domains — a personal domain and a business domain, for example — UniLink supports connecting them to different pages within your account. Build a page for each context, connect the relevant domain to each page, and run them independently. This is useful for creators who run a main personal brand page and a separate page for a specific product, course, or service.
Once your domain is live, run a full test before you announce it. Open the URL in a browser (including Chrome on mobile), confirm the padlock is showing, click every link on the page to make sure they all work, and check the page on both desktop and mobile. Custom domain issues occasionally surface only on mobile — particularly with older SSL configurations — so mobile testing isn't optional. If everything looks right, you're done.
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| Status stays "Pending" after 30 minutes | DNS record hasn't propagated, or was entered incorrectly | Check the record in your registrar's DNS panel. Confirm Type, Name, and Value exactly match what UniLink showed. Use dnschecker.org to verify global propagation status. |
| Verification fails immediately | Conflicting DNS record exists for the same name | Delete any existing A record or CNAME with the same Name field. Only one record of each type per name is valid. Save and re-verify. |
| CNAME record rejected by registrar | Trying to add a CNAME on the root domain (@) — most registrars don't allow this | Switch to an A record for root domains, or use a subdomain with a CNAME instead. Cloudflare supports CNAME on root via "CNAME flattening" — enable it in Cloudflare's DNS settings. |
| Domain shows "Active" but SSL warning appears in browser | SSL certificate hasn't fully propagated yet, or browser has cached the old state | Wait 5–10 minutes after status shows Active, then hard-refresh the browser (Ctrl+Shift+R / Cmd+Shift+R). If it persists after 30 minutes, contact UniLink support. |
| Page loads but shows wrong content | Domain connected to the wrong UniLink page or an old cached version | Check in Domain settings which page the domain is linked to. Confirm you saved the correct page association. Clear browser cache and reload. |
| SSL never issues despite Active DNS status | CAA records on your domain are blocking Let's Encrypt | In your DNS, check for CAA records. Add a CAA record: Type CAA, Name @, Value 0 issue "letsencrypt.org". Wait for propagation, then re-verify. |
When a custom domain is worth the setup
- You have a personal brand or business and want your bio link to reinforce it, not dilute it
- You're running paid ads or partnerships where brand credibility in the URL matters
- You already own a domain and just need to put it to use
- You want the flexibility to move your page's infrastructure in the future without changing your public URL
When to stick with unil.ink/username for now
- You're testing UniLink and haven't decided if you'll commit to it long-term — no point buying a domain yet
- Your brand name is already in your username and the unil.ink URL is short and readable enough
- You don't own a domain and don't want to spend on one right now
- You're setting up a page for a short-lived campaign or event that doesn't need a permanent branded URL
Frequently asked questions
Do I need to buy a domain separately, or does UniLink provide one?
You need to purchase the domain yourself from a registrar like Namecheap, GoDaddy, Cloudflare, or Google Domains. UniLink doesn't sell or register domains — it connects to domains you already own. Once you have a domain, the UniLink connection is free on paid plans and available as an add-on on the free plan.
How long does DNS propagation actually take?
Usually 15–60 minutes for most registrars, but technically up to 48 hours globally. The speed depends on the TTL of the record (set it to 300 during setup to speed things up) and how quickly your registrar pushes changes to upstream DNS servers. If you're still seeing "Pending" after 2 hours with a low TTL, double-check the record values were entered correctly — an incorrect Value field is the most common cause of stuck propagation.
Can I use my root domain (yourdomain.com without a prefix)?
Yes, using an A record. UniLink's Dashboard will show you the IP address to point to when you select A record as the connection method. The limitation is on the registrar side — most registrars don't allow a CNAME on the root domain, which is why an A record is required. Cloudflare is the exception: it supports CNAME flattening, so you can technically use a CNAME on root if your domain is managed through Cloudflare.
Will my old unil.ink/username URL still work after I connect a custom domain?
Yes. Connecting a custom domain doesn't disable your original unil.ink URL — both URLs will serve your page. If you want visitors to use only your custom domain, update all your bio links and marketing materials to point to the new URL. You can't disable the unil.ink URL, but it simply becomes a secondary access point that you don't promote.
Can I connect the same domain to multiple UniLink pages?
No — one domain maps to one page. If you want different subdomains pointing to different pages (links.yourdomain.com for one page, shop.yourdomain.com for another), each subdomain needs its own DNS record and its own domain entry in the Dashboard. Each subdomain counts as a separate domain connection in UniLink.
- Connect any domain you own to your UniLink page via a CNAME record (for subdomains) or A record (for root domains) — DNS values are provided in the Dashboard.
- Use a subdomain with a CNAME record as the default method — it works everywhere, is easier to configure, and keeps your root domain free for future use.
- Set TTL to 300 during setup to minimize propagation wait time; DNS changes typically take 15–60 minutes with a low TTL.
- SSL is issued automatically once DNS verification completes — you don't need to configure a certificate yourself.
- After your domain goes Active, update every bio link and marketing asset to the new URL — the domain doesn't promote itself.
Ready to connect your domain? Open your UniLink Dashboard and go to Settings → Domain to get started. Your branded link-in-bio URL is ten minutes away.