Vercel DNS
Vercel serves DNS only once your nameservers point at it, and then takes Mailfully's six records with no extra translation.
Vercel only answers DNS queries for a domain once that domain's nameservers are delegated to Vercel: a domain attached to a project without that delegation doesn't get a working DNS Records panel. Once delegation is in place, open the Vercel dashboard, go to Domains, select acme.com, and add each record Mailfully returned under DNS Records.
Add the records
Each of the three DKIM tokens becomes one CNAME record:
| Field | Value |
|---|---|
| Name | <token>._domainkey.mail |
| Type | CNAME |
| Value | <token>.dkim.amazonses.com |
MX carries its number in a Priority field next to the value, not folded into it:
| Field | Value |
|---|---|
| Name | send.mail |
| Type | MX |
| Value | feedback-smtp.us-east-1.amazonses.com |
| Priority | 10 |
| Field | Value |
|---|---|
| Name | send.mail |
| Type | TXT |
| Value | v=spf1 include:amazonses.com ~all |
| Field | Value |
|---|---|
| Name | _dmarc.mail |
| Type | TXT |
| Value | v=DMARC1; p=none; |
Name values here are relative to acme.com, the same trap as every other host: paste the full name Mailfully returned instead of the relative form and the zone gets appended twice.
If Vercel is not your nameserver
A domain can be attached to a Vercel project while its DNS is still managed elsewhere, and in that arrangement the DNS Records panel is the wrong place entirely: the records need to go to whichever host is actually authoritative. Check that before adding anything:
dig +short acme.com NS
If the answer doesn't list Vercel's nameservers, follow the provider guide that matches whichever host does.
Verify
dig +short <token>._domainkey.mail.acme.com CNAME
dig +short send.mail.acme.com MX
dig +short send.mail.acme.com TXT
dig +short _dmarc.mail.acme.com TXT
Each of these four should answer as Verify with dig describes.
