Setting up SPF, DKIM and DMARC at ALL-INKL: step by step in KAS
Domain at ALL-INKL.COM: the click path in KAS (Tools → DNS settings), the recommended SPF value with spf.kasserver.com, the default DMARC record p=none — and how DKIM works for own and external mail servers.
At ALL-INKL.COM all mail records live in KAS (the technical administration) under Tools → DNS settings ("DNS-Einstellungen"): edit the domain → "Add a new DNS record" → fields Name, Type, Priority, Data. For SPF, ALL-INKL recommends v=spf1 a mx include:spf.kasserver.com ~all, a DMARC record with p=none is created by ALL-INKL by default, and DKIM is available as a per-domain switch or as your own record for external mail servers.
This requires the domain's nameservers to be at ALL-INKL. Not every plan allows custom DNS records — more on that in a moment.
Step 1: Open the DNS settings in KAS
- Log in to KAS (technical administration, not the members login).
- On the left: Tools → DNS settings.
- Click the edit icon next to the domain.
- Edit an existing record or choose "Add a new DNS record"; fields: Name, Type, Priority, Data; then save.
Step 2: SPF
If an SPF record already exists, edit it — there may only be one. Otherwise "Add a new DNS record": Name stays empty, Type "TXT (SPF)", Priority 0, and in Data the value:
your-domain.dev=spf1 a mx include:spf.kasserver.com ~allBasics and handling several services: Creating an SPF record, Several sending services in one SPF.
Step 3: DKIM
For mailboxes at ALL-INKL the mail server signs as soon as DKIM is activated for the domain; ALL-INKL then generates the key and the DNS record itself. ALL-INKL does not describe in its public tutorials exactly where the switch is — user reports name the domain settings in KAS (domain → edit → "DKIM Signierung"). To verify in your own KAS; whether it works is shown by a test email to Gmail ("Show original": dkim=pass with your domain).
If you send via an external mail server or service (Microsoft 365, Google Workspace, newsletter), you create its key yourself — ALL-INKL describes this in tutorial 444: "Add a new DNS record", Name = selector plus ._domainkey (e.g. mail._domainkey), Type "TXT (DKIM)", Priority 0, Data = the public key:
mail._domainkey.your-domain.dev=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…Step 4: DMARC
According to tutorial 562, ALL-INKL creates a DMARC record with v=DMARC1; p=none; by default — observe, but block nothing. It makes sense to add a reporting address so you can see who sends in your name. To do so, edit the _dmarc record (or create it: Name _dmarc, Type TXT, Data):
_dmarc.your-domain.dev=DMARC1; p=none; rua=mailto:dmarc@your-domain.deStep 5: Check
After saving, check the domain from the outside — SPF syntax, DKIM selector, DMARC — instead of relying on the KAS display, and send a test email to a Gmail mailbox: spf=pass, dkim=pass, dmarc=pass under "Show original".
Frequently asked questions
Where do I find the DNS settings at ALL-INKL?
In KAS (technical administration) under Tools → DNS settings, then edit next to the domain. New records via "Add a new DNS record" with the fields Name, Type, Priority and Data.
Which SPF record does ALL-INKL recommend?
v=spf1 a mx include:spf.kasserver.com ~all — Name empty, Type "TXT (SPF)", Priority 0. Further sending services go into the same record; a second SPF record makes the check invalid.
Does my domain at ALL-INKL already have DMARC?
According to ALL-INKL, v=DMARC1; p=none; is set by default. That blocks nothing and, without a rua address, delivers no reports either — add at least rua=mailto:… before tightening later.
Why does the Data field not accept my DKIM key?
The field is limited to 512 characters, which is enough for 2048-bit keys. Longer keys (4096 bits) do not fit — generate a 2048-bit key at the sending service or use a CNAME if the service offers one.