Area: Episerver Campaign
Applies to versions: Not applicable

Setting up your domain

Recommended reading 

This topic describes how to configure the DNS delegation so that you can send emails via Episerver Campaign by using the sender domain of your hosted website or online shop. If you use another email server configured for your domain, answers to emails sent via Episerver Campaign will lead to this email server and not to Episerver Campaign.

DNS delegation

The DNS delegation is divided into the configuration of the sender domain and the configuration of an additional subdomain. The subdomain is used by Episerver Campaign for the technical part of the email delivery and the creation of tracking links.

When the DNS delegation is configured, Episerver Campaign sends emails with a from address like myspecialoffer@example.com. If a recipient clicks a link in an email (e.g. https://www.example.com/special-offers), Episerver Campaign converts the link to a tracking link based on the technical subdomain (e.g. https://newsletter.example.com/trackingcode). The recipient is forwarded to our tracking servers to register action data and then forwarded to the original landing page.

Please forward this information to the party responsible for your domain.

Tip: If you need to set a TTL, use the value "900 seconds". This ensures that in case of any mistakes, changes will propagate in about 15 minutes. Note also the different subdomains needed in the steps below.


To use a preferred domain, several DNS records must be created. The following configuration steps use the domain example.com.

Tip: The domain t.example.com is the technical subdomain of example.com.
  1. Create a new A-RR entry to lead tracking links to the Episerver tracking server
    • Domain: t.example.com
    • Value:
  2. Create a new MX-RR entry to lead technical responses (e.g. bounce messages) to the Episerver email server.
    • Domain: t.example.com
    • Priority: 0
    • Value: mail.srv2.de.
  3. Create a new TXT-RR entry to authorizes all IP addresses used by the Episerver email servers for your domain.
    • Domain: t.example.com
    • Value: v=spf1 include:spf.srv2.de -all
  4. Create a new CNAME-RR entry to authorizes the subdomain and ensures compatibility.
    • Domain: mailing._domainkey.t.example.com
    • Value: dkim.srv2.de.  
  5. Create a new CNAME-RR entry to authorizes the Episerver servers to use your domain for sending emails via Episerver Campaign.
    • Domain: mailing._domainkey.example.com
    • Value: dkim.srv2.de.
  6. Create a new TXT-RR entry to set a DMARC record to protect your domain from email spoofing.
    • Domain: _dmarc.example.com
    • Value: v=DMARC1; p=reject; rua=mailto:dmarc@example.com;
For information on how to set up DMARC, see the Episerver User Guide.


The example.com entries can be summarised as below.

Domain TTL   Entry Value
t.example.com 900 IN A
t.example.com 900 IN MX 0 mail.srv2.de.
t.example.com 900 IN TXT  v=spf1 include:spf.srv2.de -all
mailing._domainkey.t.example.com 900 IN CNAME  dkim.srv2.de.
mailing._domainkey.example.com 900 IN CNAME  dkim.srv2.de.
_dmarc.example.com 900 IN TXT  v=DMARC1; p=reject; rua=mailto:dmarc@example.com;
Do you find this information helpful? Please log in to provide feedback.

Last updated: Dec 11, 2020

Recommended reading