Skip to main content
This guide walks you through adding the required DNS records in Cloudflare to verify your domain with Flowforth.
Before starting, make sure you’ve already added your domain in Flowforth. You’ll need the DNS record values shown on the domain settings page.
Two Cloudflare-specific mistakes cause most failed verifications. If you’re only adding the tracking records, read these first:
  • Proxying. Cloudflare turns the orange cloud on by default for new CNAME records. The tracking record has to be set to DNS only. See CNAME Record (Tracking).
  • CAA records. Cloudflare’s CAA editor has separate fields for Flags, Tag, and CA domain name — only the hostname goes in the value field. See CAA Record (Tracking).

​
Open DNS Settings in Cloudflare

  1. Log in to your Cloudflare account
  2. Select your domain
  3. Go to DNS → Records

​
Add the MX Record

Click Add record:
  1. Set the Type to MX
  2. Enter the name from Flowforth (e.g., send) in the Name field
  3. Copy the MX Value from Flowforth into the Mail Server field
  4. Set the Priority to 10
  5. Use the default Auto for TTL
  6. Click Save
Cloudflare automatically appends your domain to the Name field. Enter only the subdomain portion — for example, type send instead of send.example.com.

​
Add the SPF Record (TXT)

Click Add record:
  1. Set the Type to TXT
  2. Enter the name from Flowforth (e.g., send) in the Name field
  3. Copy the TXT Value from Flowforth into the Content field
  4. Use the default Auto for TTL
  5. Click Save
Cloudflare automatically appends your domain to the Name field. Enter only the subdomain portion — for example, type send instead of send.example.com.

​
Add the DKIM Record (TXT)

Click Add record:
  1. Set the Type to TXT
  2. Enter the DKIM name from Flowforth (e.g., resend._domainkey) in the Name field
  3. Copy the DKIM Value from Flowforth into the Content field
  4. Use the default Auto for TTL
  5. Click Save
Cloudflare automatically appends your domain to the Name field. Enter only resend._domainkey instead of resend._domainkey.example.com.

​
Add the DMARC Record (TXT)

While not strictly required, adding a DMARC record is highly recommended. It improves deliverability and protects your domain’s reputation.
If your domain already has a DMARC record, you do not need to add another one. You can check by looking for an existing TXT record with the name _dmarc in your Cloudflare DNS records.
Click Add record:
  1. Set the Type to TXT
  2. Enter the DMARC name from Flowforth (e.g., _dmarc) in the Name field
  3. Copy the DMARC Value from Flowforth into the Content field
  4. Use the default Auto for TTL
  5. Click Save

​
Add the Tracking Records (Optional)

If you enabled click tracking or open tracking when adding your domain in Flowforth, you’ll need to add these two additional records. You can also enable tracking later from the domain detail page in Flowforth — the records will appear in your DNS table when tracking is turned on.

​
CNAME Record (Tracking)

Click Add record:
  1. Set the Type to CNAME
  2. Enter links in the Name field
  3. Enter links1.resend-dns.com in the Target field
  4. Click the Proxy status toggle so it reads DNS only and the cloud icon turns grey
  5. Use the default Auto for TTL
  6. Click Save
Cloudflare proxies new CNAME records by default. The orange cloud switches itself on as soon as you fill in the target, so you have to turn it off before saving.A proxied tracking record can never verify. Cloudflare stops publishing the CNAME and answers with its own IP addresses instead, so neither Flowforth nor the certificate authority can see where the record actually points.
Already saved it with the orange cloud on? Go to DNS → Records, click Edit on the links record, click the cloud icon so it turns grey (DNS only), and click Save. No other change is needed. To confirm the record is published correctly, look it up:
The answer should be links1.resend-dns.com. If it comes back empty, or a plain dig links.example.com +short returns IP addresses such as 104.21.x.x or 172.67.x.x, the record is still proxied.

​
CAA Record (Tracking)

A CAA record lists the certificate authorities allowed to issue certificates for your domain. The certificate for your tracking subdomain is issued by Amazon, so Amazon has to be on that list. First, check whether your domain already has CAA records. In DNS → Records, filter by type CAA, or run:
  • No CAA records (most domains). Skip this record entirely. With no CAA records published, any certificate authority may issue, and Amazon is already allowed. Adding one now would only create a way for future certificates — including your website’s — to be blocked.
  • You do have CAA records. Amazon is currently locked out, and the tracking certificate can’t be issued until you allow it. Add the record below.
Add amazon.com as a new, additional CAA record. Don’t edit or delete the entries that are already there — removing one can break certificate renewal for your website and other services on the domain.
Click Add record:
  1. Set the Type to CAA
  2. Enter @ in the Name field (this covers your root domain and its subdomains)
  3. Leave Flags set to 0
  4. Set the Tag to Only allow specific hostnames
  5. Enter amazon.com — and nothing else — in the CA domain name field
  6. Use the default Auto for TTL
  7. Click Save
Only the hostname goes in the CA domain name field. Cloudflare assembles the finished record from its three separate fields, so pasting a complete record such as 0 issue "amazon.com" into that one box publishes this instead:
That names a certificate authority which doesn’t exist. Amazon stays blocked, the certificate still can’t be issued, and the record looks fine at a glance in the Cloudflare dashboard.
Check the published record with dig example.com CAA +short. Every line should look like 0 issue "amazon.com" — a single hostname in quotes, with no nested quotes and no repeated issue. One of the lines must be amazon.com.

​
Verify in Flowforth

Once all records are added in Cloudflare, go back to your domain in Settings → Domains and click the “Records Added” button. Flowforth will check your DNS records and verify the setup in the background.
DNS changes can take anywhere from a few minutes to several hours to propagate. If verification doesn’t succeed right away, wait and try again later.

​
Troubleshooting

  • Verification failed: Double-check the records you added in Cloudflare for copy/paste errors. Make sure you’re using only the subdomain portion in the Name field (e.g., send not send.example.com).
  • DKIM and SPF verify, but the tracking records don’t: This is almost always one of two things — the links record is proxied, or a CAA record is blocking Amazon. Confirm dig links.example.com CNAME +short returns links1.resend-dns.com (not empty, and not a Cloudflare IP), and that dig example.com CAA +short either returns nothing at all or includes a well-formed 0 issue "amazon.com" line.
  • A CAA record that looks wrong: If dig example.com CAA +short shows a value with quotes inside quotes, such as 0 issue "0 issue \"amazon.com\"", the full record string was pasted into Cloudflare’s CA domain name field. Edit that record and set the value to just amazon.com.
  • Priority conflict: If priority 10 is already in use on another MX record, use a different value like 20 or 30.
  • Still not verifying after 72 hours: Contact support@flowforth.co and we’ll help you debug the issue.
If you need help, contact support@flowforth.co.