How to Configure DNS for UniLink (CNAME, A Records, and Propagation Guide)
How to Configure DNS for UniLink (CNAME, A Records, and Propagation Guide)
Set up your custom domain correctly the first time — learn which DNS records to use, how to configure them at GoDaddy, Namecheap, or Cloudflare, and how long to wait before it goes live.
cname.unil.ink for subdomains like www. For root domains (yourdomain.com), use an A record pointing to UniLink's IP. Set TTL to 300–600 seconds for faster testing. Propagation usually completes in 15–60 minutes, but can take up to 48 hours in rare cases.
Connecting a custom domain to your UniLink page makes your brand feel professional and trustworthy. Instead of sharing a long unil.ink/username link, visitors land directly on yourname.com. The process involves two things: adding the right DNS records at your domain registrar, and waiting for those records to spread across the internet. This guide walks through both steps in detail, including the exact settings for the most popular DNS providers.
What DNS Configuration Does
DNS (Domain Name System) is the internet's address book. When someone types your domain into a browser, their computer queries DNS servers to find out which server to connect to. Without the right DNS records, your domain points nowhere — or worse, to an old server.
UniLink uses two types of records for custom domains. A CNAME record is an alias — it says "this hostname is really just another name for that other hostname." An A record is more direct — it maps a hostname to a specific IP address. Each has its place depending on which part of your domain you're connecting.
When UniLink detects that your DNS records are correctly pointing to the platform, it automatically provisions an SSL certificate and activates your custom domain. You don't need to configure anything else in UniLink beyond entering the domain name in your settings.
How to Get Started With DNS Configuration
- Add your domain in UniLink — Go to Dashboard → Settings → Custom Domain. Enter the domain you want to use (e.g.,
www.yourname.comoryourname.com- Log in to your domain registrar — This is wherever you bought your domain: GoDaddy, Namecheap, Cloudflare, Google Domains, etc. Look for a section called "DNS Management," "DNS Records," or "Advanced DNS."
- Choose the right record type — For a subdomain like
www.yourname.com, create a CNAME record. For a root/apex domain likeyourname.com, create an A record. See the section below for exact values.- Enter the record values — For CNAME: set the Name/Host to
wwwand the Value/Target tocname.unil.ink. For A record: set the Name/Host to@and the Value/Target to UniLink's IP (shown in your Dashboard DNS setup screen).- Set the TTL — Change the TTL (Time to Live) to 300 or 600 seconds while you're setting things up. This means DNS changes propagate faster. You can raise it to 3600 or higher later once your domain is working.
- Save and wait — Save your DNS records. Propagation typically takes 15–60 minutes. For most providers it's faster. You can check progress with a tool like dnschecker.org — enter your domain and watch the green checkmarks fill in globally.
- Verify in UniLink — Return to Dashboard → Settings → Custom Domain. UniLink checks your DNS automatically every few minutes. Once verified, the status badge changes to "Active" and your domain goes live.
How to Use DNS Settings at Major Providers
- GoDaddy — Log in → My Products → click the domain → DNS. Scroll to the Records table. Click Add to create a new record. Select type CNAME, enter
wwwas the Host, andcname.unil.inkas Points To. Set TTL to "Custom" and enter 600. - Namecheap — Dashboard → Domain List → Manage → Advanced DNS. Under Host Records, click Add New Record. Select CNAME Record, set Host to
www, Value tocname.unil.ink, and TTL to 5 minutes (300 seconds). - Cloudflare — Select your domain → DNS → Records → Add record. Choose CNAME, set Name to
www, Target tocname.unil.ink. Important: toggle the orange cloud icon to grey (DNS only, not proxied). If Cloudflare proxies the request, UniLink cannot verify your domain ownership. - Google Domains / Squarespace Domains — DNS → Manage custom records → Create new record. Type: CNAME, Host name:
www, Data:cname.unil.ink, TTL: 300. - Root domain on any provider — If you want
yourname.com(no www) to work, create an A record with Host set to@and Value set to the UniLink IP shown in your dashboard. Some providers (like Cloudflare) support CNAME flattening at the root — in that case you can use a CNAME at@too. - Both root and www — To cover both, create both the A record at
@and the CNAME atwww. Then set up a redirect in your registrar soyourname.comredirects towww.yourname.com(or vice versa) to avoid duplicate content. - Check propagation with online tools — Use dnschecker.org or whatsmydns.net. Enter your domain and record type. You'll see a world map of DNS servers showing whether they've picked up your changes yet. Green checks = propagated.
Key Settings Explained
| Setting | What it controls | Best practice |
|---|---|---|
| CNAME record | Points a subdomain (www, blog, store) to another hostname instead of an IP address | Use for www and all subdomains — never at the root domain |
| A record | Points any hostname directly to an IPv4 address | Use for root/apex domains (@ or bare domain) |
| TTL (Time to Live) | How long DNS resolvers cache your record before re-checking | Set to 300–600 during setup; raise to 3600 after domain is live |
| Proxy status (Cloudflare) | Whether Cloudflare intercepts traffic or passes it through | Must be set to DNS Only (grey cloud) for UniLink verification |
| Host / Name field | The subdomain part of the record (what comes before your domain) | Use www for www subdomain, @ for root, exact name for others |
How to Get the Most Out of DNS Configuration
The biggest mistake people make with DNS is impatience — checking every 2 minutes and making changes before propagation finishes. DNS propagation is not instant because resolvers around the world cache your old records for the duration of their TTL. If your TTL was 86400 (24 hours) before you made the change, some resolvers won't update for a full day.
The solution is to lower your TTL before you make important DNS changes. If you know you'll be switching your domain to UniLink next Tuesday, log into your registrar on Monday and lower the TTL to 300. That way when you actually switch, the old record expires quickly everywhere. After the domain is verified and working, raise the TTL back to 3600 or higher for better performance.
If you want both your root domain and www to work, you need records for both. Many registrars let you set up a redirect from root to www (or www to root) at the registrar level — this is the cleanest approach because it avoids duplicate content issues in search engines. Pick one canonical version and redirect the other.
For troubleshooting, the command line is your friend. Run dig CNAME www.yourdomain.com on Mac/Linux or nslookup www.yourdomain.com on Windows to see exactly what DNS is returning for your domain. If the answer doesn't show cname.unil.ink, your record isn't configured correctly or hasn't propagated yet.
Troubleshooting Common Issues
| Problem | Likely cause | Fix |
|---|---|---|
| Domain shows "Pending" in UniLink after 2+ hours | DNS record not saved correctly, or old TTL causing slow propagation | Double-check record values at your registrar; use dnschecker.org to confirm propagation |
| CNAME record rejected at root domain | DNS spec does not allow CNAME at the apex — most registrars block this | Use an A record at the root, or use a provider that supports CNAME flattening (Cloudflare, Route 53) |
| Domain resolves but shows wrong site | Old A record or another CNAME still pointing to a previous host | Delete all old records for the same hostname before adding the new one |
| Cloudflare-managed domain won't verify | Proxy (orange cloud) is intercepting requests before UniLink can see them | Set the DNS record to DNS Only (grey cloud) in Cloudflare DNS panel |
Pros
- Custom domain makes your brand look more professional and trustworthy
- CNAME records are flexible — easy to update if UniLink ever changes IPs
- Low TTL during setup speeds up the testing and verification cycle
- DNS changes are reversible — you can always point back to a previous host
Cons
- Propagation delay means you cannot instantly verify a new DNS setup
- Root domain CNAME limitations require an A record or a supporting provider
- Misconfigured records at Cloudflare (proxy enabled) silently block verification
Frequently Asked Questions
How long does DNS propagation take?
Most DNS changes propagate globally within 15–60 minutes when TTL is set to 300–600 seconds. With higher TTLs (like the default 86400 = 24 hours), it can take up to 48 hours for all resolvers worldwide to update. Lower your TTL before making changes to speed this up.
Can I use my root domain (without www) with UniLink?
Yes. Create an A record pointing @ (your root domain) to the UniLink IP shown in your dashboard. If you also want www to work, add a CNAME for www pointing to cname.unil.ink. Then set a redirect at your registrar so one version redirects to the other.
Why does my domain work in some countries but not others?
DNS propagation is not simultaneous worldwide. Different DNS resolvers pick up changes at different rates based on their cache TTL. Use dnschecker.org to see which regions have propagated and which haven't. Wait for full propagation — usually complete within a few hours.
I deleted the old records but the wrong site still shows up. Why?
Your browser or local ISP has the old DNS result cached. Try opening the domain in a private/incognito window, on a different device, or on a mobile network. You can also flush your local DNS cache: on Windows run ipconfig /flushdns, on Mac run sudo dscacheutil -flushcache.
Do I need to do anything in UniLink after setting DNS?
UniLink checks your DNS automatically every few minutes after you save the domain in settings. Once it detects the correct records, it verifies the domain and provisions SSL automatically. You don't need to manually trigger anything — just wait for the "Active" status to appear.
Key Takeaways
- Use a CNAME record pointing to
cname.unil.inkfor subdomains like www; use an A record for root domains - Set TTL to 300–600 seconds before making DNS changes to speed up propagation
- Cloudflare users must set the record to DNS Only (grey cloud) — the proxy blocks UniLink verification
- Use dnschecker.org to monitor global propagation progress and confirm your records are live
- UniLink verifies your domain and provisions SSL automatically once DNS propagates — no manual steps needed
Ready to connect your custom domain?
Set up your professional link-in-bio page with a custom domain in minutes. UniLink handles SSL, verification, and routing automatically once your DNS is configured.
Get Started FreeCreate Your Free Link-in-Bio Page
Join thousands of creators using UniLink. 40+ blocks, analytics, e-commerce, and AI tools — all free.
Get Started Free