Enable DKIM at Mittwald
In mStudio open the domain under "Email" and enable DKIM; Mittwald adds the records with its own name servers.
mStudio shows the SPF value next to the domain.
Other senders sign separately
Every service sending on behalf of the domain needs its own DKIM key with its own selector: the newsletter tool, the CRM, Microsoft 365. The records do not interfere because each lives under a different selector. DMARC then covers all of them.
How to add the DKIM record at Mittwald
The way to the Mittwald DNS editor:
- In mStudio open the project and select the domain under "Domains".
- Type and name as shown by the mail provider: usually CNAME or TXT under selector._domainkey. The selector name goes before _domainkey, the host appends the rest of the domain.
- Open "DNS", edit or create the record, save.
Typical mistakes at Mittwald
- Selector missing or misspelled in the name, so the receiver finds no key.
- TXT value truncated for long keys or split into several records.
- CNAME next to other records on the same name.
- DKIM enabled in the control panel but the name servers are elsewhere and the record is missing there.
Verify and keep an eye on it
After saving, the change at Mittwald usually applies within minutes. The checker below queries the authoritative name servers and shows right away whether the DKIM record is read correctly. DomainWarn keeps checking the record afterwards and alerts you when it changes or disappears, for example after a migration or one click too many in the DNS editor.
Frequently asked questions
- Why does the checker find no DKIM record after enabling it at Mittwald?
- Either the name servers are not at Mittwald and the record is missing there, or the selector differs from the common ones. Enter the selector name from the Mittwald control panel in the DKIM checker.
- Which key length is right?
- 2048 bits. 1024 bits is considered too short, longer keys do not fit every DNS editor.