Add InboxNest DNS records in Cloudflare
Add InboxNest records in Cloudflare DNS → Records, and keep applicable CNAME records set to DNS only.
When this guide applies
Use this page when InboxNest identifies Cloudflare as the DNS host. This is ordinary Cloudflare DNS, not Cloudflare Email Routing.
Where to sign in
Sign in at the Cloudflare dashboard and select the domain.
Cloudflare DNS navigation
Open DNS → Records. Add a record for each row shown in InboxNest.
Enter the InboxNest records
Copy Type, Host, and Value from the InboxNest setup screen. In Cloudflare, the root host is often @ or the bare domain, depending on how the dashboard presents the field.
- Type
- CNAME
- Host / Name
- the-host-shown-in-inboxnest
- Value / Target
- record-value-shown-in-inboxnest
- TTL
- Use the provider default, or the TTL shown in InboxNest if one is listed.
Host, Value, Priority, and TTL
- Name is InboxNest’s Host.
- Target / Content is InboxNest’s Value.
- Priority appears on MX records only.
- TTL can stay Auto unless InboxNest shows a specific value.
Use DNS only, not the proxy
For any CNAME or hostname verification record InboxNest displays, set Proxy status to DNS only (the gray cloud). Do not proxy those hostnames. MX and TXT records cannot be proxied; Cloudflare will not show a proxy toggle for those types, and you should not look for one.
What not to delete
Keep website and unrelated records. On Direct MX, change only the MX records InboxNest is replacing. On forwarding, leave current MX records in place.
Return to InboxNest
Save the records, return to InboxNest, and click Verify setup.
Troubleshooting
The most common Cloudflare issue is an orange-cloud proxy on a CNAME that must stay DNS only. Confirm the zone is the authoritative one for the domain, then retry verification. See DNS troubleshooting.