Contents of this article
In the control panel you can set up the records for SPF, DMARC and your mail servers in one go, without typing them out by hand. You see in advance exactly what changes and what disappears. This page covers what is in those presets and when you are better off not using them.
Why this lives in DNS
Most email problems are not mail problems but DNS problems. Mail that lands in the spam folder, invoices sent in your name, a newsletter service that suddenly stops getting through: in almost all of those cases, something is wrong in your domain's DNS.
The tricky part is not that it is complicated, but that it has to be exact. One missing dot in an MX record, or an SPF rule with a space in the wrong place, and it doesn't work, without any error message. That is why the editor has a preset per mail configuration: it sets the whole set correctly in one go.
What a preset sets up exactly
There are two presets. Both replace the MX records and the SPF record on your main domain and add a DMARC record. Providers that issue their own key or token per domain, such as Proton Mail, are deliberately not included: those values differ per customer and so can't be set automatically.
Hostage email
| Type | Name | Value |
|---|---|---|
| MX | @ | mail.hostage.eu (priority 10) |
| TXT | @ | v=spf1 a include:_spf.hostage.nl -all |
| TXT | _dmarc |
v=DMARC1; p=reject; rua=mailto:dmarc@hostage.nl; aspf=s; adkim=r; ri=86400; |
Note the p=reject: this preset puts DMARC into enforcement straight away. Read below why that is not always wise on an existing domain.
Soverin
| Type | Name | Value |
|---|---|---|
| MX | @ | mx.soverin.net. (priority 10) |
| MX | @ | mx02.soverin.net. (priority 20) |
| MX | @ | mx03.soverin.net. (priority 30) |
| TXT | @ | v=spf1 include:soverin.net ~all |
| CNAME | soverin1._domainkey |
soverin1._domainkey.soverin.net. |
| CNAME | soverin2._domainkey |
soverin2._domainkey.soverin.net. |
| CNAME | soverin3._domainkey |
soverin3._domainkey.soverin.net. |
| CNAME | _dmarc |
reject._dmarc.soverin.net. |
For Soverin, DKIM is part of the preset, because Soverin works with fixed selectors that point to its own zone. That makes this the only preset that sets your three DKIM records correctly right away.
What you see before anything changes
Applying a preset takes two steps. In the first, you choose the provider. In the second, you don't get a summary but the actual plan:
- What gets added: all records from the table above, with their exact values and priorities.
- What gets replaced: your existing MX and SPF records are listed by name, with their current value, so you can see what you lose.
- What stays: your DKIM records are listed separately, so you don't have to guess whether they survive the change.
Below that is a warning we deliberately left in: if the configuration goes wrong, you can no longer receive mail, and mail that doesn't arrive can't be recovered. The apply button stays greyed out until you explicitly tick that you understand this.
That tick box is not a formality. A DNS change to your MX records is the only action in the control panel where a mistake has silent consequences: there is no outage notice, and you only find out when someone tells you that you aren't replying.
Why your DKIM records stay
DKIM keys are unique per domain and are issued outside the DNS editor. If a preset cleaned them up because it doesn't list them itself, the signing of your outgoing mail would break and there would be no way back: the key is gone and has to be issued again. That is why no preset touches any record under *._domainkey.
There is one exception, and it makes sense: if a preset does list such a record explicitly, as Soverin does with its own three selectors, then that definition simply wins.
When you are better off not using a preset
On a new domain, a preset is the quickest good choice. On a domain that has been in use for years, there is one thing to find out first: who sends mail on your behalf. The SPF record from the preset only covers the mail servers of that one provider. If your accounting software, your web shop, your newsletter service or the contact form on your site also sends mail with your domain as the sender, they are not included.
Combined with the p=reject from the Hostage preset, that is no small matter: mail from those forgotten senders is rejected from then on, without you being told. Almost every organisation setting this up for the first time turns out to have forgotten such a sender.
You check it with these three tools
The editor sets records, but it doesn't assess them. If you want to know whether everything is right, use our public tools. They are free, need no account and also work for domains that aren't hosted with us.
- Check an SPF record (in Dutch): resolves your entire include chain and counts the real number of DNS lookups. This shows you whether adding to your SPF record has pushed you over the limit of ten.
- Read a DMARC report (in Dutch): shows per sender who is sending mail on behalf of your domain and what aligns. This is the tool that helps you find those forgotten senders.
- Explain a bounce message (in Dutch): if mail comes back with an error code, this tells you what it means.
What the editor doesn't do
It doesn't check your records and gives no advice. No warning appears if you have two SPF records, if your DMARC record contains no report address or if your DKIM key is missing. The editor shows what is in your zone and sets what you choose; we leave the assessing to the tools above and to ourselves.
It also doesn't read your DMARC reports for you and keeps no history of who has sent mail on behalf of your domain. If you have dozens of systems sending mail in your name, a specialised DMARC service is a better choice than what we offer. We would rather tell you that now than have you find out for yourself.
Two conditions
The presets only work if your domain uses our nameservers, because we then manage the zone ourselves. If your DNS is hosted elsewhere, you can copy the records by hand from the tables above: they aren't secret and work the same everywhere. And you need edit rights on the domain; with a reseller account, you arrange that from your customer's environment.
Further reading
- Domain protection for email (in Dutch): the step-by-step plan behind these records
- Setting up SPF, DKIM and DMARC: what each record does
- Email on your own domain (in Dutch)
- Back to the knowledge base
Was this article helpful?
Thank you for your feedback.
Thank you. What were you missing? Let us know at support@hostage.nl and we will add it to the article.
Related articles
- Set up an out-of-office reply in webmail Set up an automatic reply that starts and stops on the days you choose.
- Using webmail: logging in and finding your way Logging in to webmail and finding your way around folders, messages and settings.
- Change the webmail language and time zone Change the language and time zone of webmail in the preferences.
- Forward email automatically from webmail Forward mail from a mailbox to another address automatically using webmail.
Still stuck?
Send us a message. We will help you, usually within one working day.