The DKIM records for Fastmail
Fastmail requires three CNAME records for DKIM: fm1, fm2 and fm3 under _domainkey. Each points to a host at Fastmail that contains your domain in its name, following the pattern fm1.your-domain.dkim.fmhosted.com.
All three are mandatory. Through the CNAMEs Fastmail manages the keys itself. Domains that were at Fastmail before 2018 additionally know the older selector mesmtp; it plays no role for new setups.
fm1._domainkey CNAME fm1.example.com.dkim.fmhosted.com
fm2._domainkey CNAME fm2.example.com.dkim.fmhosted.com
fm3._domainkey CNAME fm3.example.com.dkim.fmhosted.comHow to set up DKIM for Fastmail
The steps in the Fastmail admin interface and at the DNS host:
- In the Fastmail settings open “Domains” and add the domain; Fastmail shows the records needed.
- Create three CNAME records at the DNS host: fm1._domainkey, fm2._domainkey and fm3._domainkey with the targets shown.
- At Cloudflare keep the proxy off for these CNAMEs (“DNS only”).
- Repeat the check at Fastmail and check in the DKIM checker with the selector fm1.
Click path at Fastmail
Official guide from Fastmail: Manual DNS configuration(opens in a new tab)
Publishing at the DNS host
DKIM records always live at selector._domainkey. Most DNS editors append the domain themselves, so you only enter the part before it. CNAME records for DKIM must not sit behind a proxy. The guides per host below show where the record is created in the respective DNS editor.
Verify and keep an eye on it
The DKIM checker below queries the key under the selector and checks structure and length. You see whether the records for Fastmail are publicly visible. DomainWarn keeps checking them afterwards and alerts you when a key disappears or changes.