Skip to main content

Connect a Custom Domain

Use your own domain (like go.yourbrand.com) to create professional, branded short links.

What You'll Get​

✅ Branded Short Links

  • go.yourbrand.com/promo instead of snipzr.com/abc123
  • Builds trust with your audience
  • Reinforces brand identity

✅ Your Own Zone

  • A dedicated space for your custom domain links
  • Complete control over slugs and analytics
  • Professional appearance

✅ Full Features

  • Track clicks and analytics
  • Generate QR codes
  • API access
  • Bulk operations

Before You Start​

Requirements​

  • ✅ Domain Access: You own a domain or can purchase one
  • ✅ DNS Access: Ability to edit DNS records
  • ✅ Snipzr Plan: Basic or Professional plan

Decide: Subdomain or Root Domain?​

You have two valid strategies. Pick the one that matches your situation:

StrategyExampleBest forNotes
Subdomain (recommended)go.yourbrand.comMost teams, quickest setupWorks on almost every DNS provider using a standard CNAME. Doesn’t disrupt your main website.
APEX / root (shortest links)yourbrand.link or yourbrand.comDedicated “short domain” use casesRequires a DNS provider that supports apex CNAME-like behavior (often called CNAME flattening, ALIAS, or ANAME) to point the root to a hostname target.
tip

If your apex/root domain currently hosts your main website or other services, use a subdomain for Snipzr (e.g., go.yourbrand.com).
Use APEX/root only when the domain is dedicated to short links (or you fully understand the impact of moving root traffic to Snipzr).

This guide covers both paths:

  • Path A: Subdomain setup (go.yourbrand.com)
  • Path B: APEX/root setup (yourbrand.com or yourbrand.link)

Step-by-Step Setup​

Step 1: Add Domain to Snipzr​

  1. Log in to Snipzr

    • Go to Zones → Add New

  2. Click "Add New"

    • Enter your domain (subdomain or root)
    • Click Next

  3. Note the DNS Configuration

    • Snipzr shows the DNS records you need
    • Keep this page open - you'll need these values

Step 2: Configure DNS​

Go to your DNS host (where your DNS records are managed) and add the records Snipzr shows.

For a subdomain like go.yourbrand.com, you’ll add:

  • a CNAME for go → Snipzr target

Example: Cloudflare (subdomain)​

Type: CNAME
Name: go
Target: ark.snipzr.com
Proxy status: DNS only (gray cloud - important!)
TTL: Auto

Example: Namecheap (subdomain)​

CNAME Record:
Host: go
Value: ark.snipzr.com
TTL: Automatic

Example: GoDaddy (subdomain)​

Type: CNAME
Name: go
Value: ark.snipzr.com
TTL: 1 Hour

Path B: APEX / root domain setup (shortest links)​

For a root domain like yourbrand.com, you generally cannot use a normal CNAME at the apex due to DNS constraints.

To connect root to a hostname target (like ark.snipzr.com), you need a provider feature typically called:

  • CNAME flattening (Cloudflare), or
  • ALIAS (Namecheap / Porkbun / Squarespace Domains), or
  • ANAME (some DNS providers)

APEX/root DNS examples (common providers)​

Cloudflare (CNAME flattening at apex)​

Cloudflare supports CNAME flattening at the zone apex (@) and returns IP answers instead of a CNAME chain:

Create:

Type: CNAME
Name: @
Target: ark.snipzr.com
Proxy status: DNS only (recommended for SaaS integrations)
TTL: Auto

Namecheap (ALIAS at apex)​

Namecheap ALIAS lets you set Host @ to a hostname and resolves to the correct A/AAAA at request time:

Create:

Type: ALIAS
Host: @
Value: ark.snipzr.com
TTL: Automatic

Porkbun (ALIAS – CNAME flattening)​

Porkbun documents “ALIAS - CNAME flattening” for the root domain:

Create:

Type: ALIAS - CNAME flattening
Host: (blank / root)
Answer/Value: ark.snipzr.com

Squarespace Domains (ALIAS)​

Squarespace Domains supports ALIAS records for pointing one domain to another domain:

Create an ALIAS at @ to Snipzr’s target hostname.

Important: not every “Alias” works for SaaS hostname targets​

Some DNS providers have “alias” features that primarily target their own cloud resources, not arbitrary third-party hostnames.

Examples:

If you’re on Route 53 or Azure DNS and your goal is APEX/root → Snipzr hostname target, the simplest options are:

  • use a subdomain (Path A), or
  • move DNS hosting to a provider that supports generic apex flattening/ALIAS/ANAME (Cloudflare is the most common choice)

Other DNS Providers​

No matter the provider, the goal is the same:

  • Subdomain path: go CNAME → Snipzr target
  • APEX path: @ via CNAME-flattening / ALIAS / ANAME → Snipzr target

For detailed registrar/DNS-specific guides:

Step 3: Verify Domain​

DNS changes take time to propagate (about a minutes to 24 hours, typically 5-30 minutes).

  1. Return to Snipzr

    • Click DNS Configured

  2. Confirm Creation

  • Review the details
  • Click Create Zone
  1. Wait for Propagation
    • Give DNS 5-30 minutes to update
    • Snipzr checks your DNS records
    • Status updates:
      • Pending: Waiting for verification
      • Verified: DNS records found!

  • Troubleshooting Verification (if needed)

    • Wait longer (up to 24 hours)
    • Double-check DNS records are correct
    • Ensure Cloudflare proxy is OFF (gray cloud)
    tip

    If you’re connecting the APEX/root and verification fails:

    • Confirm your DNS provider supports apex CNAME-like behavior to a hostname target (CNAME flattening / ALIAS / ANAME).
    • On some platforms, “Alias” features target only their own cloud resources (for example, Route 53 Alias and Azure DNS Alias are not generic flatteners for arbitrary hostnames in all cases):
    • Check for conflicting root records (existing A/AAAA records for @ can prevent your apex alias/flattening from taking effect).
    • If your DNS host can’t do apex hostname targeting, switch to the subdomain strategy or migrate DNS to a provider that supports it (Cloudflare / DNSimple / DNS Made Easy).

  1. Wait for SSL Provisioning

    • After verification, Snipzr provisions SSL certificate automatically
    • Takes about 2-30 minutes
    • You don't need to do anything

  2. Check Status

    • Zone shows as Active when ready to use

Step 4: Set as Default (Optional)​

Make your custom domain the default for new links:

  1. Go to Zones → Your Zones
  2. Find the zone for your custom domain
  3. Choose "Set as Default"

Now all new links use your branded domain automatically!

  1. Go to "Links"
  2. Click "Create New"
  3. Add "URL to shorten"
  4. Customize the slug
  5. Give it a recognizable title
  6. Click "Create"

Result:

https://go.yourbrand.com/promo

Beautiful! 🎉

Understanding User Zones​

When you connect a custom domain, Snipzr creates a User Zone - a dedicated container for your domain's links. (Available under "Your Zones" in the "Zones" dashboard)

What's a User Zone?​

  • Container: Holds all links for one domain
  • Organization: Keeps your links separate from Snipzr default domains
  • Analytics: Track performance per zone
  • Management: Bulk operations, exports, settings

Zone vs Domain​

Think of it this way:

  • Domain: The URL people see (go.yourbrand.com)
  • Zone: The management space in Snipzr where you organize those links

One zone = one domain. The terms are often used interchangeably.

Common Use Cases​

Marketing Campaigns​

https://go.yourbrand.com/summer-sale
https://go.yourbrand.com/newsletter-june
https://go.yourbrand.com/social-promo
https://link.company.com/handbook
https://link.company.com/onboarding
https://link.company.com/tools

Product Launches​

https://get.product.com/launch
https://get.product.com/demo
https://get.product.com/pricing

Event Promotion​

https://go.event.com/register
https://go.event.com/schedule
https://go.event.com/speakers

Troubleshooting​

Domain Verification Fails​

Problem: Snipzr can't verify your domain

Solutions:

  1. Wait Longer: DNS can take up to 24 hours
  2. Check DNS Records: 
    # SUBDOMAIN path (example: go.yourbrand.com)
    dig CNAME go.yourbrand.com

    # APEX/root path (example: yourbrand.com)
    # Many flattening/ALIAS providers return A/AAAA answers at the apex, so check A/AAAA:
    dig A yourbrand.com
    dig AAAA yourbrand.com
  3. Verify Cloudflare Proxy: Must be OFF (gray cloud)
  4. Check for Typos: Ensure exact match with Snipzr's instructions
  5. Contact Support: If stuck after 24 hours

SSL Not Provisioning​

Problem: Domain verified but SSL pending

Causes:

  • DNS not fully propagated globally
  • Rate limits (rare)

Solutions:

  1. Wait 24 Hours: Give DNS time to propagate worldwide
  2. Contact Support: After 24 hours

Problem: Custom domain links don't work

Checklist:

  • ✅ Link format: Correct slug, URL and zone
  • ✅ Link status: Not disabled or deleted
  • ✅ Domain status: "Active" (blue icon) in dashboard?
  • ✅ Browser cache: Try incognito mode
  • ✅ Network: Try different device/network

"DNS_PROBE_FINISHED_NXDOMAIN"​

Problem: Browser can't find domain

Meaning: DNS record doesn't exist

Solutions:

  1. Verify DNS record created correctly
  2. Wait for DNS propagation
  3. Flush local DNS cache: 
    # macOS
    sudo dscacheutil -flushcache

    # Windows
    ipconfig /flushdns

    # Linux
    sudo systemd-resolve --flush-caches

Maintenance​

Regular Tasks​

Monthly:

  • Review and delete old links
  • Check broken destination URLs
  • Review analytics
  • Update slugs if needed

Quarterly:

  • Audit DNS records
  • Optimize based on performance

Security​

Best Practices:

  • ✅ Enable 2FA on domain registrar
  • ✅ Keep WHOIS privacy enabled
  • ✅ Monitor for unauthorized DNS changes
  • ✅ Review zone access regularly

Domain Renewal​

Don't forget:

  • Set domain auto-renewal at registrar
  • Add calendar reminder 60 days before expiration
  • Update payment method if needed

Cost Summary​

One-Time:

  • Domain purchase: $0 (if using subdomain of owned domain) or $10-50/year
  • Setup time: 15 minutes - 24 hours

Recurring:

  • Snipzr plan: Basic or Professional
  • Domain renewal: ~$12/year (if new domain)

Next Steps​

Your custom domain is connected! Now:

  1. Create branded links
  2. Customize slugs
  3. Generate QR codes
  4. Use the API for automation

Need a Domain?​

Don't have a domain yet? Learn how to purchase one:

Learn More​

Need Help?​

Your brand, your domain, your short links! 🚀✨