One of the final parts of the onboarding process requires some modification to your domain's DNS configuration. This is normally hosted with your domain's registrar (where you've purchased your domain from), but in some cases may also be hosted by a third-party if you are assuming control of your existing domain from a previous hosting or technical service provider. It is important to understand who is responsible for hosting your website's DNS records, as you will require access to make the documented configuration changes. Implementing these records is broken down into two main steps: E-mail Validation and Website Launch. Below you will find some general examples of how you or a technical contact may go about adding these records to your domain's DNS and brief explanations of their purpose.

...

• DKIM record set: A group of CNAME records used for digitally signing e-mails generated by the Socast platform. Digitally signing e-mails provides a layer of security by verifying that an e-mail sent from your domain originated from where it was supposed to. In some cases this can aid deliverability as it allows a receiver to better identify if the message can be trusted or not. These records must be correctly implemented to activate e-mail functionality on the platform for your website.
• Website record set: A list of CNAME and A records for pointing your website domain to the Socast platform. This record set should always be added last and should only be done when you are ready to officially launch your Socast website. You will also need to make sure that the proper domain names have been added to your Website Settings before configuring these records to prevent any service interruption.

2. DKIM Signing

This section is similar to creating the records for domain verification. These records are responsible for digitally signing any e-mails sent on behalf of your website's domain which ensures that they are delivered, unaltered from where they originated from. While these records are not a requirement for e-mail capabilities on the Socast platform, it is strongly advised that you still implement these records as they can impact deliverability of any e-mail based communications. From our example CSV file above (or your own CSV file if you are following along), you will need to make note of the following information:

...

All Socast platform customers are provided with an ongoing, free SSL certificate to secure their websites with. This is done automatically and supports the adding and removing of additional website aliases (providing they are properly configured in your DNS settings). Upon either launching a new site or modifying an existing site's host names in the backend and all the required DNS records are in place, an SSL certificate will be automatically generated (or modified if already existing) to include the names configured in your Website Settings. Normally these changes can be seen within an hour, approximately - however if it has been longer than 12 hours and your site still isn't secured with an SSL certificate, please reach out to Client Services for further investigation. The certificate can only ever contain names that resolve via DNS to the Socast platform. So if there are any host names configured in the backend that have either been removed from your DNS configuration or are otherwise absent, these names will not be included in your SSL certificate.