# Add MailBlastr DNS records on Vercel

> Publish the SPF, DKIM, and DMARC records MailBlastr generates for your domain using Vercel’s Domains DNS records UI.

This guide walks through adding the DNS records MailBlastr generates for a domain using **Vercel**. Add your domain in MailBlastr first 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 for your exact DKIM record and region.

This applies when Vercel manages your domain’s DNS — i.e. the domain’s nameservers point at Vercel (Vercel is your DNS provider), not just when a project is attached to the domain.

## Open the DNS Records editor

1. **Open Domains** — In the Vercel dashboard go to your **team/account → Settings → Domains** (or the project’s **Domains** tab) and select your domain.
2. **Find DNS Records** — Scroll to the **DNS Records** section, which lists current records and has an **Add** form.
3. **Add each record** — In the Add form choose the **Type**, set **Name**, fill in **Value**, and click **Add**. Repeat for all six records.

> **Warning:** Vercel’s **Name** field is the subdomain relative to your domain — leave it blank or `@` for the apex, otherwise enter just the prefix. Use `mailblastr._domainkey`, `send`, and `_dmarc` (not the full hostname). Vercel appends your domain automatically.

## DKIM — TXT

Add **one** TXT record holding your domain’s DKIM public key.

**DKIM — TXT**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | TXT | No | A single DKIM key record. |
| `Name` | mailblastr._domainkey | No | Vercel appends `.yourdomain.com`, giving `mailblastr._domainkey.yourdomain.com`. `mailblastr` is the fixed selector MailBlastr uses. |
| `Value` | v=DKIM1; k=rsa; p=<public key> | No | The DKIM key record holding your domain’s public key. |
| `TTL` | 60 | No | Vercel default (seconds); leave as-is. |

## SPF — MX + TXT on the send subdomain

MailBlastr uses the custom MAIL FROM subdomain `send.yourdomain.com`. Set **Name** to `send` for both records. Vercel’s MX form has a dedicated **Priority** field.

**SPF — MX**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | MX | No | Receives bounce and complaint feedback for the MAIL FROM subdomain. |
| `Name` | send | No | Resolves to `send.yourdomain.com`. |
| `Value` | feedback-smtp.us-east-1.amazonses.com | No | Region-specific feedback host. Replace `us-east-1` with your domain’s region. |
| `Priority` | 10 | No | Vercel’s separate MX priority field. |
| `TTL` | 60 | No | Vercel 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`. |
| `Value` | v=spf1 include:amazonses.com ~all | No | Authorizes Amazon SES for the MAIL FROM subdomain. Enter without surrounding quotes. |
| `TTL` | 60 | No | Vercel default. |

## DMARC — TXT on _dmarc

**DMARC — TXT**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Type` | TXT | No | DMARC policy record. |
| `Name` | _dmarc | No | Resolves to `_dmarc.yourdomain.com`. |
| `Value` | v=DMARC1; p=none; | No | A monitoring policy to start with. |
| `TTL` | 60 | No | Vercel default. |

> **Note:** Vercel-specific gotchas: only the **DNS Records** editor matters here — attaching the domain to a project does not publish these mail records; enter the **Name** as the bare prefix (`send`, `_dmarc`, `mailblastr._domainkey`), not the full domain; and do not add the SPF to the apex — it belongs on the `send.` subdomain.

Vercel’s DNS propagates quickly given its low default TTL. Once all six records are added, return to MailBlastr and [re-verify the domain](https://www.mailblastr.com/docs/api/domains-verify).