Custom Domains
DNS and SSL Setup - What Records to Add
A reference for all DNS records Convot generates for custom help center and email domains.
This page is a reference for the DNS records Convot generates. If you’re looking for setup steps, see:
Help center domain records
When you set up a custom domain for your help center, Convot generates two records:
CNAME - traffic routing
| Field | Value |
|---|---|
| Type | CNAME |
| Host |
help.acme.com (your chosen subdomain) |
| Value | origin.convot.help |
This record points your subdomain at Convot’s origin. Cloudflare intercepts requests at the edge, terminates TLS, and forwards them to the origin.
TXT - domain ownership verification
| Field | Value |
|---|---|
| Type | TXT |
| Host | _cf-custom-hostname.help.acme.com |
| Value | A unique token Convot generates for your domain |
Cloudflare requires this to confirm you own the domain before issuing a TLS certificate.
SSL certificates
Convot uses Cloudflare for SaaS to provision and renew TLS certificates automatically. You do not manage certificates yourself. Once both records are verified, Cloudflare issues a DV certificate and renews it before it expires.
Email domain records
When you set up a custom email domain, Convot generates six records:
Ownership TXT
Proves you control the domain to Convot’s sending infrastructure.
| Field | Value |
|---|---|
| Type | TXT |
| Host | The subdomain you entered |
| Value | A unique verification token |
MX - inbound mail
Routes customer reply emails into Convot. Some DNS providers want the priority and value in one field (e.g. Route 53). Convot shows both a separate priority field and a combined value.
| Field | Value |
|---|---|
| Type | MX |
| Host | The subdomain you entered |
| Priority | 10 |
| Value | Convot’s inbound mail host |
SPF TXT
Tells receiving mail servers that Convot is authorized to send email on behalf of your domain.
| Field | Value |
|---|---|
| Type | TXT |
| Host | The subdomain you entered |
| Value |
v=spf1 include:mail.convot.io -all (or similar) |
DKIM - signing
DKIM signs outgoing messages cryptographically so recipient inboxes verify they came from you and weren’t tampered with.
| Field | Value |
|---|---|
| Type | CNAME (or TXT depending on your provider) |
| Host | A _domainkey subdomain Convot specifies |
| Value | Convot’s DKIM signing host |
Return-Path CNAME
Bounces and delivery notifications are sent to this address. Configuring it improves deliverability scores.
| Field | Value |
|---|---|
| Type | CNAME |
| Host |
pm-bounces.<your-subdomain> (Convot specifies) |
| Value | Convot’s bounce handling host |
DMARC TXT
DMARC instructs receiving servers what to do when an email fails SPF or DKIM checks. It protects your domain from being spoofed by third parties.
| Field | Value |
|---|---|
| Type | TXT |
| Host | _dmarc.<your-subdomain> |
| Value | v=DMARC1; p=none; rua=... |
General tips
- Add all records before clicking Verify. Missing even one can cause delivery problems.
- If your DNS provider combines priority and value into one field (MX records), paste the combined value Convot shows you.
- TTL setting does not affect whether records are accepted, only how fast they propagate. A lower TTL (e.g. 300 seconds) during initial setup speeds up propagation.
- If a record shows as error after propagation, check that you didn’t accidentally add an extra dot at the end of a hostname, or that your provider didn’t duplicate the zone name (a common cause of incorrect CNAME values).
Was this article helpful?
Thanks for your feedback!