Custom domains
Point your own domain at a hosted Jant blog — blog.example.com, www.example.com, or example.com.
How to set up a custom domain
At your DNS provider, point the domain at:
domains.jant.blog
The record type depends on whether it's a subdomain or root — see below. Certificate issuance, routing, and ownership verification are handled by Jant automatically.
Subdomain
For blog.example.com or www.example.com:
| Type | Name | Value |
|---|---|---|
| CNAME | blog |
domains.jant.blog |
Root domain (apex)
DNS standards don't allow CNAME at the root. Use an equivalent record type instead:
| Provider | Root record type |
|---|---|
| Cloudflare | CNAME (auto-flattened) |
| Route 53 (AWS) | ALIAS |
| DNSimple | ALIAS |
| Hover | ANAME |
| Namecheap (Premium DNS) | ALIAS |
Configuration:
| Type | Name | Value |
|---|---|---|
| CNAME / ALIAS | @ (root) |
domains.jant.blog |
Provider doesn't support CNAME / ALIAS at the root
Two options:
- Switch DNS provider. Your registrar doesn't have to move with it; Cloudflare offers free DNS hosting.
- Fall back to an A record. Point the root at
5.223.63.72.
Option 1 is recommended: the CNAME path follows platform changes automatically, while A records require manual updates whenever the address changes.
FAQ
Serving both www and root
Each blog is bound to a single custom domain — the canonical URL visitors see.
If you want the other version (apex or www) to be reachable and redirect to the canonical URL, handle it at the DNS / CDN layer. Cloudflare recommends Single Redirects; one rule is enough:
Source URL: https://www.example.com/*
Target URL: https://example.com/$1
Status: 301
Enabling Cloudflare Proxy (orange cloud)
Proxy can stay on. Jant verifies "did the request reach Jant?" — it doesn't care what's in between.
If something goes wrong, check the Cloudflare side first:
- SSL/TLS mode: set it to Full. Flexible causes redirect loops; Full (strict) may reject connections during the brief window before the certificate is issued.
- Page Rules / Cache Rules: don't apply forced-HTTPS rewrites or caching to
/.well-known/*— that path must reach Jant unmodified. - Error codes:
525/526mean TLS negotiation failed between Cloudflare and Jant, usually a wrong SSL/TLS mode;522means the request didn't reach Jant at all, typically a DNS issue.
If it still doesn't work, switch Proxy to DNS only (gray cloud) for the initial setup, then turn it back on once the domain is live.