Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/subratomandal/dyeink/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Give your blog a professional touch by connecting your own custom domain. Instead of using a Dyeink subdomain, your blog can be accessible at blog.yourname.com or any domain you own.
All custom domains are automatically secured with SSL/TLS certificates, ensuring your blog is served over HTTPS.

​
Prerequisites

Before setting up a custom domain, you’ll need:
  • A registered domain - You must own a domain (e.g., from Namecheap, GoDaddy, Cloudflare, etc.)
  • DNS access - Ability to modify DNS records for your domain
  • A subdomain (recommended) - e.g., blog.yourname.com rather than the root domain
We recommend using a subdomain like blog.yourname.com rather than your root domain (yourname.com) for easier DNS management.

​
Setting Up Your Custom Domain

​
Step 1: Add Your Domain

1

Navigate to Settings

Go to Settings in your admin panel
2

Open Publication tab

Click the Publication tab
3

Enter your domain

In the Custom Domain field, enter your domain (e.g., blog.yourname.com)
4

Save settings

Click Save to register your domain
After saving, you’ll see DNS configuration instructions.

​
Step 2: Configure DNS

You’ll need to add a CNAME record to your domain’s DNS settings: 
Type: CNAME
Name: blog (or your subdomain)
Value: cname.vercel-dns.com
The exact steps vary by provider, but generally:
  1. Log in to your domain registrar (Namecheap, GoDaddy, etc.)
  2. Find the DNS settings or DNS management page
  3. Add a new CNAME record
  4. Set the name/host to your subdomain (e.g., blog)
  5. Set the value/target to cname.vercel-dns.com
  6. Save the record
Namecheap
  • Go to Domain List > Manage > Advanced DNS
  • Add a CNAME record
GoDaddy
  • Go to My Products > DNS > Add Record
  • Select CNAME
Cloudflare
  • Go to DNS > Add Record
  • Select CNAME
  • Important: Turn OFF the proxy (grey cloud)
If you use Cloudflare, make sure to:
  • Turn OFF the proxy (click the cloud icon until it’s grey)
  • OR set SSL mode to “Full (Strict)” in SSL/TLS settings
Otherwise, verification may fail.

​
Step 3: Verify Your Domain

After adding the DNS record:
  1. Wait 5-10 minutes for DNS propagation
  2. Return to the Publication settings page
  3. Click Verify Connection
DNS changes can take anywhere from 5 minutes to 48 hours to propagate, though it’s usually much faster.

​
Step 4: SSL Certificate Issuance

Once verification succeeds:
  1. You’ll see a “Domain Verified!” message
  2. An SSL certificate will be automatically generated
  3. This process takes 5-20 minutes
  4. Your blog will be accessible via HTTPS at your custom domain
You don’t need to do anything during SSL issuance. The process is fully automated.

​
Domain Status

Your domain can be in one of these states:
You’ve added the domain but haven’t configured DNS yet, or DNS records haven’t propagated.Action: Add the CNAME record and wait for propagation.
DNS is configured correctly and verification succeeded. SSL certificate is being generated.Action: Wait 5-20 minutes for SSL issuance.
Your domain is fully active with SSL. Your blog is accessible at your custom domain.Action: None - everything is working!
Verification failed, usually due to incorrect DNS configuration.Action: Double-check your DNS records and try verifying again.

​
DNS Configuration Examples

Here are the exact DNS records you need for common scenarios:

​
Using a Subdomain (Recommended)

For blog.yourname.com:
TypeNameValueTTL
CNAMEblogcname.vercel-dns.comAuto

​
Using www

For www.yourname.com:
TypeNameValueTTL
CNAMEwwwcname.vercel-dns.comAuto

​
Multiple Subdomains

You can only connect one domain per blog, but you could use:
  • blog.yourname.com for your main blog
  • writing.yourname.com for a separate Dyeink blog (requires another account)

​
Managing Your Domain

​
Viewing Domain Status

To check your domain status:
  1. Go to Settings > Publication
  2. View the domain card
  3. Check the status indicator

​
Removing a Custom Domain

To disconnect your custom domain:
  1. Go to Settings > Publication
  2. Click Disconnect or Remove
  3. Confirm the action
Removing your custom domain will make your blog accessible only via your Dyeink subdomain (e.g., yourname.dyeink.com).

​
Troubleshooting

Common causes:
  • DNS records not yet propagated (wait longer)
  • Incorrect CNAME value (must be exactly cname.vercel-dns.com)
  • Cloudflare proxy enabled (turn off or use Full Strict SSL)
  • Existing DNS records conflicting (remove old records)
Check your DNS: Use DNS Checker to verify your CNAME is propagated globally.
SSL issuance can take up to 20 minutes after verification. If it’s been longer:
  • Try disconnecting and reconnecting the domain
  • Ensure no CAA records are blocking certificate issuance
  • Contact support if the issue persists
If you see SSL/TLS warnings:
  • Wait for SSL certificate to finish issuing (can take 20 minutes)
  • Check that you’re accessing via HTTPS not HTTP
  • Clear your browser cache
  • Try in an incognito/private window
If you see “Domain already in use”:
  • The domain is connected to another Dyeink blog
  • Remove it from the other blog first
  • Or use a different subdomain
Cloudflare users must:Option 1 (Recommended):
  • Turn OFF the proxy (grey cloud) for the CNAME record
Option 2:
  • Keep proxy ON (orange cloud)
  • Set SSL/TLS mode to “Full (Strict)”
  • Go to SSL/TLS > Overview > Full (Strict)

​
Advanced Topics

​
DNS Propagation Time

DNS propagation refers to how long it takes for DNS changes to spread across the internet:
  • Minimum: 5-10 minutes
  • Typical: 30 minutes to 2 hours
  • Maximum: Up to 48 hours (rare)
Lower your TTL (Time To Live) value to 300 seconds before making DNS changes to speed up propagation.

​
SSL/TLS Certificates

Dyeink automatically provisions SSL certificates from Let’s Encrypt:
  • Issued: Automatically after domain verification
  • Renewed: Automatically before expiration
  • Type: Let’s Encrypt TLS certificate
  • Coverage: Your custom domain only

​
Using Apex/Root Domains

While possible, using apex domains (yourname.com without a subdomain) is more complex:
  • Some DNS providers don’t support CNAME on root domains
  • You may need to use ALIAS or ANAME records (provider-dependent)
  • We recommend using a subdomain like blog.yourname.com instead

​
Best Practices

Use Subdomains

Use blog.yourname.com instead of root domains for easier management

Lower TTL First

Set DNS TTL to 300 seconds before making changes for faster propagation

Test After Changes

Wait 10-15 minutes after DNS changes before verifying

Keep DNS Simple

Remove conflicting DNS records before adding the CNAME

​
Next Steps

Analytics

Track traffic to your custom domain

Posts

Start publishing on your custom domain

Build docs developers (and LLMs) love

Get started for freeTalk to us