Troubleshooting Short Domains
Solutions to common problems when connecting and using custom domains (user zones) in Snipzr.
Domain Verification Issues
Problem: Domain Verification Fails
Symptoms:
- Verification status shows "Failed" or "Pending" for over 24 hours
- Error message: "Could not verify domain ownership"
Possible Causes:
- DNS records not properly configured
- DNS propagation still in progress
- Cloudflare proxy enabled (should be off)
- Typo in DNS records
Solutions:
1. Check DNS Records
Verify your records are correct:
# Check CNAME record
dig CNAME go.yourdomain.com
# Alternative tool
nslookup go.yourdomain.com
Expected results:
- CNAME should point to
ark.snipzr.com
2. Wait for DNS Propagation
DNS changes can take time:
- Typical: 15-30 minutes
- Maximum: 48 hours
Check propagation globally:
3. Cloudflare Users: Disable Proxy
If using Cloudflare:
- Go to DNS settings
- Find your CNAME record
- Click the orange cloud to make it gray
- Save changes
Important: Must be "DNS only" (gray cloud), not "Proxied" (orange cloud)
4. Check for Typos
Common mistakes:
- ❌ Wrong subdomain:
go.yourdomain.comvsgoo.yourdomain.com - ❌ Wrong target:
ark.snipzr.comvsredirect.snipzr.link
5. Clear DNS Cache
Clear your local DNS cache:
# macOS
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder
# Windows
ipconfig /flushdns
# Linux (systemd)
sudo systemd-resolve --flush-caches
# Linux (nscd)
sudo /etc/init.d/nscd restart
6. Contact Support
If verification fails after 48 hours:
- Contact support
- Include your domain name
- Attach screenshot of DNS records
SSL Certificate Issues
Problem: SSL Not Provisioning
Symptoms:
- Domain verified but SSL status shows "Provisioning" for over 24 hours
- SSL status shows "Failed"
Possible Causes:
- DNS not fully propagated globally
- Rate limits hit (rare)
Solutions:
1. Wait for Global Propagation
Even if DNS works locally, it needs to propagate worldwide:
- Check multiple global DNS servers
- SSL provisioning requires global propagation
- Wait 24-48 hours
2. Contact Support
If SSL fails after 48 hours:
- Email support@snipzr.com
- Include domain name
- Mention steps already tried
Link Redirect Issues
Problem: Links Give 404 or Don't Redirect
Symptoms:
- Custom domain links show 404 error
- Links don't redirect to destination
- Browser shows "Page not found"
Checklist:
1. Verify Domain Status
Check in Snipzr dashboard:
- ✅ Domain status: "Active" (blue icon)
2. Check DNS Resolution
# Should resolve to Snipzr IP
dig go.yourdomain.com
# Or
nslookup go.yourdomain.com
3. Test from Different Networks
- Try from different device
- Try from mobile data (not WiFi)
- Try from incognito/private browser
- Try after clearing cache
4. Verify Link Exists
- Go to Snipzr dashboard
- Check link actually exists in that zone
- Verify slug spelling
- Check link is enabled (not disabled)
5. Check for Typos
❌ Wrong: go.yourdomain.com/sa1e
✅ Correct: go.yourdomain.com/sale
DNS Configuration Problems
Problem: "DNS_PROBE_FINISHED_NXDOMAIN"
What it means: Browser can't find your domain - DNS record doesn't exist.
Solutions:
-
Verify DNS Record Created
- Log into DNS provider
- Check CNAME record exists
- Verify it's not disabled
-
Check Record Name
✅ Correct: go (for go.yourdomain.com)
❌ Wrong: go.yourdomain.com -
Wait for Propagation
- New records need 15 min - 48 hours
- Check whatsmydns.net
-
Flush Local Cache (see above commands)
Problem: DNS Points to Wrong Server
Symptoms:
- Domain resolves but shows different website
- Links redirect to unexpected place
Solutions:
-
Check CNAME Target
dig CNAME go.yourdomain.comShould show:
ark.snipzr.com -
Remove Conflicting Records
- Check for multiple records with same name
- Remove old/unused records
- Keep only the Snipzr CNAME
-
Check Cloudflare Settings
- Page Rules might interfere
- Workers might intercept requests
- Disable proxying (gray cloud)
Domain Management Issues
Problem: Can't Edit or Delete Domain
Symptoms:
- "Delete" button not available
- Can't change domain settings
- Error when trying to modify
Solutions:
-
Check Permissions
- Verify you're the account owner
-
Active Links
- Can't delete domain with active links
- Move or delete all links first
- Then delete domain
-
Default Domain
- Can't delete default domain
- Set another domain as default first
-
Zone created recently
- Zones deletion cooldown is in effect
Problem: Domain Shows "Pending" Forever
Symptoms:
- Added domain days ago
- Still shows "Pending" status
- Can't verify or use
Solutions:
-
Delete and Re-add
- Remove the pending domain
- Wait 5 minutes
- Add it again fresh
-
Contact Support
- Provide domain name
- Include date added
Performance Issues
Problem: Slow Redirects
Symptoms:
- Links take long to redirect
- Noticeable delay before destination loads
Possible Causes:
- DNS resolution slow
- Destination server slow
- Network issues
Solutions:
-
Optimize DNS
- Use faster DNS provider (Cloudflare, Route 53)
- Lower TTL for faster updates (but not too low)
-
Check Destination
- Test destination URL directly
- Slow destination = slow redirect perception
-
Geographic Issues
- Test from different locations
- Snipzr uses global CDN
Problem: Intermittent Availability
Symptoms:
- Links work sometimes, fail other times
- Different behavior on different networks
Solutions:
-
Check DNS TTL
- Very low TTL can cause issues
- Recommended: 300-3600 seconds
-
ISP DNS Issues
- Try using public DNS (8.8.8.8, 1.1.1.1)
- ISP DNS might be caching wrong data
Common Error Messages
"Invalid domain format"
Cause:
- Domain format doesn't meet requirements
- Special characters or invalid TLD
Solution:
- Use alphanumeric and hyphens only
- Check for typos
- Ensure valid TLD (.com, .net, etc.)
"This domain is already connected"
Cause:
- Domain already connected to another Snipzr account
Solution:
- Prove ownership to transfer
"DNS verification failed"
See "Domain Verification Issues" section above.
Getting Additional Help
Before Contacting Support
Gather this information:
- Domain name
- DNS provider
- Error messages (screenshot)
- Steps already tried
- DNS record screenshots
How to Contact
Email: support@snipzr.com
Include:
- Clear description of problem
- Domain name
- Screenshots
- Results from DNS checks
DNS Diagnostic Commands
Run these and include results:
# Basic DNS check
dig go.yourdomain.com
# Trace DNS path
dig +trace go.yourdomain.com
# Check from specific DNS server
dig @8.8.8.8 go.yourdomain.com
# All record types
dig ANY go.yourdomain.com
Preventive Measures
Setup Checklist
Before connecting domain:
- Have DNS access
- Know your DNS provider
- Domain has proper nameservers
- No conflicting records
- Cloudflare proxy disabled (if using)
- 24-48 hours available for propagation
Best Practices
-
Document Everything
- Keep record of DNS settings
- Screenshot configurations
- Note verification tokens
-
Test Thoroughly
- Test from multiple devices
- Test from different networks
- Test in incognito mode
-
Monitor Regularly
- Check domain status weekly
- Verify SSL certificate not expiring
- Monitor link analytics
-
Maintain Access
- Keep DNS provider credentials secure
- Enable 2FA on DNS provider
- Document renewal dates
Related Resources
Still having issues? We're here to help!