Custom Domains & DNS Configuration
Point your own domain to an imagine.bo project. We support Domain Connect for automatic setup with compatible providers, and manual configuration for everyone else.
How It Works
Provider Detection & Flow Routing
When you submit a domain, the backend checks whether your DNS provider supports the Domain Connect protocol by querying the _domainconnect TXT record on your zone. Based on that result, one of two flows begins:
There is no separate pre-check step. Support detection happens when you submit the domain, not before. The UI presents both options and the backend determines which path applies.
Supported Domain Connect Providers
1. Automatic Setup (Domain Connect)
For compatible DNS providers
Go to Project Settings → Domains.
Enter your domain (e.g., example.com) and click Connect.
The backend detects your provider. If Domain Connect is supported, you are redirected to your DNS provider's authorization page.
Review and approve the changes on your provider's page.
After approval, you are redirected back to imagine.bo. Your domain status moves to Verifying (dns_pending internally).
The backend polls DNS every 30 seconds for up to 10 minutes. When your records propagate, status becomes Active and SSL provisioning begins automatically.
2. Manual Configuration
For providers that do not support Domain Connect
If your provider does not support Domain Connect, add the following records through your registrar's dashboard, then click Verify.
Root / Apex Domain (example.com)
Use an A Record:
Cloudflare users: If you have "Proxied" mode enabled, Cloudflare flattens the CNAME automatically. You can use a CNAME for @ pointing to domains.imagine.bo instead of the A record. Both verify correctly.
WWW Subdomain (www.example.com)
Add a CNAME Record:
Custom Subdomain (e.g., app.example.com)
Add a CNAME Record:
3. Verification Logic
How DNS records are validated
Once records are saved, click Verify (or wait for the automatic post-callback poll after auto setup). The backend runs the following checks every 30 seconds for up to 10 minutes:
CNAME check
Resolves the domain and compares the result against domains.imagine.bo. Used for subdomains and providers that support CNAME flattening.
A record check (fallback)
If the CNAME check fails or is not applicable (apex domains), resolves the domain's A record and compares it against 52.201.69.110.
If either check passes:
- Status → Active
- SSL provisioning starts immediately (status:
provisioning)
If neither check passes within 10 minutes:
- Status → Failed
- Re-trigger verification by clicking Verify again
DNS propagation can take a few minutes to 24 hours depending on your TTL and registrar. If status stays Verifying for more than 30 minutes, check your records match the values above exactly.
4. Status Reference
Domain lifecycle states
5. SSL / TLS
Automatic certificate provisioning
Once a domain becomes Active, imagine.bo automatically provisions a TLS certificate via Let's Encrypt. No manual configuration is required. The TLS status field tracks progress separately from domain status.
SSL certificates are provisioned and renewed automatically. You do not need to purchase, upload, or configure certificates separately.