Configure DKIM (and SPF) records for your sending domain

This guide outlines the steps required to configure the DKIM (and SPF if applicable) records provided by njuko via Amazon Web Services (AWS SES) with the main domain hosting providers (OVHcloud, IONOS, 123 Reg, GoDaddy).

Proper authentication configuration is essential to secure your sending domain and ensure optimal deliverability of your event communications.

1. Retrieve your DKIM records

Before configuring your DNS, retrieve your DKIM records in njuko:

1. Go to Setup → Edition settings → Advanced options → Custom email sender address

2. Enter the email address you want to use

3. Once the domain is valid, the DKIM and SPF records will be displayed

4. Copy the values provided

You will usually receive three DKIM CNAME records. All must be added to your DNS configuration.

1.1 SPF configuration (if provided)

If an SPF record is also provided:

• Do not replace your existing SPF record

• Combine it with the one provided by njuko

• Your domain administrator can merge both values into a single SPF entry

Incorrect SPF configuration may affect email deliverability.

2. Configure records in your domain provider

2.1 OVHcloud

Management location: Client Area > Domains > [Your Domain] > DNS Zone

Steps:

1. Click Add an entry

2. Select the record type CNAME

3. Subdomain: Enter the key (e.g. sig1._domainkey)

   ⚠️ Do not add your domain name at the end

4. Target: Paste the AWS value (e.g. sig1.dkim.amazonses.com.)

Example:

Subdomain	Type	Target
njk1._domainkey	CNAME	njk1.dkim.amazonses.com

2.2 IONOS (1&1)

Management location: Domains & SSL > DNS

Steps:

1. Click Add record, then select CNAME

2. Hostname: Enter the key (e.g. sig1._domainkey)

3. Points to: Enter the AWS value (e.g. sig1.dkim.amazonses.com)

Example:

Hostname	Type	Points to
sig2._domainkey	CNAME	sig2.dkim.amazonses.com

2.3 123 Reg (United Kingdom)

Management location: Manage Domains > Advanced DNS

Steps:

1. Under Add new record, select CNAME

2. Hostname: Enter the key (e.g. sig1._domainkey)

3. Destination CNAME: Enter the AWS value (e.g. sig1.dkim.amazonses.com.)

2.4 GoDaddy

Management location: Domain Settings > DNS tab

Steps:

1. Click Add New Record and select CNAME

2. Name: Enter the key (e.g. sig1._domainkey)

3. Value: Enter the AWS value

4. Recommendations and common errors

4.1 Final dot requirement

Some providers (such as OVHcloud or 123 Reg) require a final dot at the end of the target value.
If you encounter an error, verify whether the trailing dot is required.

4.2 DNS propagation

DNS changes may take between 1 hour and 24 hours before being detected by AWS.

4.3 Duplicate domain entry

Do not copy your domain name into the “Name/Host” field.
If you see something like:

sig1._domainkey.yourdomain.com.yourdomain.com

remove the duplicated portion.

5. Validation

Once all DKIM records have been added, AWS will automatically detect them. This validation process may take up to 24 hours.
If the records are still not validated after propagation, contact the njuko support team.

---

If you are unsure about the best configuration for your event, our team is happy to guide you.