# Add MailBlastr DNS records on Cloudflare

> Publish the SPF, DKIM, and DMARC records MailBlastr generates for your domain using the Cloudflare dashboard.

This guide walks through adding the DNS records MailBlastr generates for a domain using the **Cloudflare** dashboard. Before you start, add your domain in MailBlastr to generate the records — see [Managing domains](https://www.mailblastr.com/docs/domains/managing) — and keep the [DNS records](https://www.mailblastr.com/docs/domains/dns) reference open, since the exact values (your DKIM record and your region) come from there.

Cloudflare must be your domain’s **authoritative DNS** (your nameservers point at Cloudflare) for these records to take effect. If your domain only uses Cloudflare as a proxy in front of another DNS host, add the records at the authoritative host instead.

## Open the DNS records editor

1. **Select your domain** — Log in at **dash.cloudflare.com** and click the domain (zone) you want to send mail from.
2. **Go to DNS → Records** — In the left sidebar choose **DNS**, then **Records**. This lists every record on the zone and has the **Add record** button.
3. **Add each record** — Click **Add record** once per entry below. Choose the **Type**, fill in **Name** and the target, and save. Repeat for all six records.

## DKIM — TXT

Add **one** TXT record holding your domain’s DKIM public key. In Cloudflare’s **Name** field you can enter the full host or just the part before your domain — Cloudflare appends the zone automatically and displays the full name.

**DKIM — TXT**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | TXT | No | A single DKIM key record. |
| `Name` | mailblastr._domainkey | No | Cloudflare auto-appends `.yourdomain.com`, giving `mailblastr._domainkey.yourdomain.com`. `mailblastr` is the fixed selector MailBlastr uses. |
| `Content` | v=DKIM1; k=rsa; p=<public key> | No | The DKIM key record holding your domain’s public key. |
| `TTL` | Auto | No | Leave at the Cloudflare default. |

## SPF — MX + TXT on send.yourdomain.com

MailBlastr uses a custom MAIL FROM subdomain, `send.yourdomain.com`, which needs both an MX and a TXT record. In the **Name** field enter `send` — Cloudflare appends the zone. MX and TXT records cannot be proxied, so there is no cloud toggle on these rows.

**SPF — MX**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | MX | No | Routes bounce and complaint feedback for the MAIL FROM subdomain. |
| `Name` | send | No | Resolves to `send.yourdomain.com`. |
| `Mail server` | feedback-smtp.us-east-1.amazonses.com | No | Region-specific feedback host. Replace `us-east-1` with your domain’s region. |
| `Priority` | 10 | No | MX priority. |
| `TTL` | Auto | No | Cloudflare default. |

**SPF — TXT**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | TXT | No | SPF policy for the MAIL FROM subdomain. |
| `Name` | send | No | Same host as the MX — resolves to `send.yourdomain.com`. |
| `Content` | v=spf1 include:amazonses.com ~all | No | Authorizes Amazon SES to send for the MAIL FROM subdomain. Paste exactly; Cloudflare quotes it for you. |
| `TTL` | Auto | No | Cloudflare default. |

## DMARC — TXT on _dmarc.yourdomain.com

**DMARC — TXT**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | TXT | No | DMARC policy record. |
| `Name` | _dmarc | No | Resolves to `_dmarc.yourdomain.com`. |
| `Content` | v=DMARC1; p=none; | No | A monitoring policy to start with; tighten to `quarantine` or `reject` later. |
| `TTL` | Auto | No | Cloudflare default. |

> **Note:** Cloudflare-specific gotchas: do not append a trailing dot to CNAME/MX targets in the dashboard (Cloudflare handles it); and if you have an existing SPF TXT at the apex, leave it — MailBlastr’s SPF lives on the `send.` subdomain, not the root.

Cloudflare’s edge DNS usually propagates within a minute or two. Once all six records are in, return to MailBlastr and [re-verify the domain](https://www.mailblastr.com/docs/api/domains-verify).