Domain authentication
      Back to home
      1. Help Center
      2. Send email pitches
      3. Domain authentication

      How to set DKIM keys in OVH 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 OVH. If you use any other domain provider or do not know how to enable authentication in Prowly, please refer to this article first.

       

      Log into your OVH account.

      1. On the right-side menu choose the "Product and Services" button.

        Screenshot 2022-12-19 at 13.29.04 
      2. By clicking on the proper row, go to the DNS zone of your domain.

        Screenshot 2022-12-19 at 13.32.13
      3. On the right side click "Add an entry".
        Screenshot 2022-12-19 at 13.34.06
      4. You should see a pop-up window with the 3 steps of adding a record. First, choose the type of record from the records list. 

        Screenshot 2022-12-19 at 13.40.31

      5. Next, copy all the data to the correct fields: subdomain (a record name - purple) and value (record data - blue) as in the below pattern. For the first TXT record, the subdomain field leaves empty. 


      Screenshot 2022-12-19 at 13.42.37

       

      Please, remember that some domain providers add domain names by default so you have to skip this part in the Subdomain field like below.


      Screenshot 2022-12-19 at 15.23.58
      Screenshot 2022-12-19 at 15.25.17

      6.    After successful record adding you should see a green bar with the information.

      Screenshot 2022-12-19 at 13.43.05

      7.   Make double-check between records in Prowly App and your DNS zone if everything is filled         correctly. 

      Screenshot 2022-12-19 at 15.26.28

      Now after you successfully configure all the DNS records, you may need to wait up to 48 hours for all the records to be updated in the DNS zone. This is an inevitable process due to how the propagation of DNS records works.