GoDaddy DNS
GoDaddy treats the Name field as relative to your domain, which is what doubles the suffix on Mailfully's DKIM records.
GoDaddy's DNS records live under My Products: select the domain, open DNS, then Manage DNS, and add each record Mailfully returned there.
Add the records
GoDaddy's record form has four fields: Type, Name, Value, and TTL, plus Priority on MX records. The Name field is relative to the zone, and GoDaddy appends acme.com on save. Enter these relative values directly, for a domain managed at the acme.com zone:
| Field | Value |
|---|---|
| Type | CNAME |
| Name | <token>._domainkey.mail |
| Value | <token>.dkim.amazonses.com |
| TTL | 1 Hour |
Do this three times over, once per token Mailfully returned.
| Field | Value |
|---|---|
| Type | MX |
| Name | send.mail |
| Value | feedback-smtp.us-east-1.amazonses.com |
| Priority | 10 |
| Field | Value |
|---|---|
| Type | TXT |
| Name | send.mail |
| Value | v=spf1 include:amazonses.com ~all |
| Field | Value |
|---|---|
| Type | TXT |
| Name | _dmarc.mail |
| Value | v=DMARC1; p=none; |
Read the saved records back
Don't try to settle this from GoDaddy's record list. Whether it shows a saved name in the relative form, <token>._domainkey.mail, or in full, the display says nothing about whether the zone got appended underneath it. Confirm against the dig output below: if the CNAME resolves to the DKIM target, the name is right no matter how GoDaddy shows it.
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 TXTGoDaddy's own record list will not settle this; the lookups will. Verify with dig gives the answer each one should return.