How to set DKIM keys in Ionos properly

Set DKIM keys in your domain settings smoothly and easily to go through the domain authentication process fast and with no obstacles.

This article contains instructions on how to configure DNS records necessary for domain authentication in Prowly, when your domain provider is Ionos. If you use any other domain provider or do not know how to enable authentication in Prowly, please refer to this article first.

1. Log into your Ionos account.

2. Choose the Manage domain button from the hints on the right side. 

Screenshot 2023-01-03 at 14.54.40

Or choose the Domains & SSL tab from the pop-up menu in the upper left corner. 

Screenshot 2023-01-08 at 22.17.26

3. Choose the domain you want to authenticate and go to the DNS section. 

Screenshot 2023-01-03 at 14.58.08

4. Click Add record button. 

Screenshot 2023-01-08 at 22.40.36

5. You will be switched to a different view. You can see the list of available record types.
We will be based on the TXT and CNAME records regarding the DKIM keys we want to set. The order of addition does not matter. 

Screenshot 2023-01-08 at 22.42.03

6. Click on the row of the particular type of record. You will be switched to the next view. Those fields are the record settings and should be filled according to Prowly.

Screenshot 2023-01-08 at 23.14.33

7. Copy all the data from Prowly domain authentication settings to your DNS records in the below order: Host Name/Record Name - purple; Value - blue. The TTL (Time To Live) field you can leave by default or change up to you. Compare data again between Prowly and the preview of the record settings and click save if it is correct. 

Screenshot 2023-01-08 at 23.09.44

Screenshot 2023-01-08 at 23.34.06

8. You should be notified about the successfully added record. 

Screenshot 2023-01-08 at 23.42.29

9. Add the rest of the records by analogy. 

Screenshot 2023-01-08 at 23.46.10

10. Check again if you add all four required records (DKIM keys) and if everything is correct. 

Screenshot 2023-01-08 at 23.48.23

Please, remember that your server needs some time to propagate new records, so the domain authentication could not be immediate.