Custom Domains & SSL
Every project deployed on Exovon receives an automatic *.exovon.co.in edge subdomain. You can attach custom branded domains (such as app.domain.com or apex domain.com) with automated TLS 1.3 certificates provisioned across our global Anycast edge network.
Configuration Walkthrough
Connect and verify your custom domain in three simple steps:
Add Your Domain in the Exovon Dashboard
Open your project dashboard, navigate to the Domains section, enter your domain name (e.g. app.domain.com or domain.com), and click Add Domain.
Publish DNS Records at Your Registrar
Log in to your DNS provider (Cloudflare, GoDaddy, Namecheap, Route 53) and configure the routing and verification records provided in your dashboard:
| Domain Target | Type | Host / Name | Target / Value | TTL |
|---|---|---|---|---|
| Subdomain (e.g. app) | CNAME | app (or www) | router.exovon.co.in | Auto (300s) |
| Apex / Root (Primary) | A | @ | 172.67.182.1 (backup: 104.21.70.1) | Auto (300s) |
| Ownership Challenge | TXT | _exovon-challenge | [token-from-dashboard] | Auto (300s) |
Automatic SSL Validation & Traffic Activation
Once DNS records propagate globally (typically 2 to 10 minutes), our edge network verifies the challenge token and provisions a dedicated TLS 1.3 certificate with zero downtime.
Subdomain vs. Apex Domain DNS Rules
Standard DNS RFC specifications prevent standard CNAME records on root apex domains (domain.com) because a CNAME cannot coexist with mandatory root records (SOA, NS, MX).
Subdomains (app.domain.com, api.*)
Universally supported across 100% of DNS registrars using standard CNAME records. Point host app to router.exovon.co.in.
Apex Domains (domain.com)
For universal registrar support, add an A record pointing @ to Anycast IP 172.67.182.1. Alternatively, use CNAME Flattening (Cloudflare) or ALIAS records (Route 53) pointing to router.exovon.co.in.
Cloudflare DNS Configuration Notice
If your domain DNS is hosted on Cloudflare, set the CNAME record status to DNS Only (Grey Cloud) during initial challenge verification. Enabling the Orange Cloud proxy during verification can prevent our edge from validating the challenge and cause redirect loops.
Verifying DNS Propagation
Inspect whether your DNS records have propagated globally using terminal diagnostics:
# 1. Verify CNAME routing to Exovon Anycast Edge
dig CNAME app.yourdomain.com +short
# 2. Verify challenge token TXT record
dig TXT _exovon-challenge.app.yourdomain.com +short
# 3. Test TLS 1.3 handshake and certificate issuer
curl -Iv https://app.yourdomain.com 2>&1 | grep -E "SSL certificate|HTTP/"Frequently Asked Questions
How long does custom domain verification take?
Most DNS providers propagate records within 2 to 15 minutes. Once records are detected globally, Exovon activates your domain and issues the SSL certificate within 60 seconds.
Are SSL certificates renewed automatically?
Yes. Exovon manages automated 90-day renewal cycles for all active custom domains with zero downtime or manual intervention required.