For optimal deliverability, we recommend setting up custom authentication for your mail sent via Communications Enterprise. Setting up this authentication will require a few updates to your Domain Name Service (DNS) settings, which may require the assistance of your IT team. These changes are necessary to ensure SPF and DKIM authentication are correct and tied to your sending domain.
TIP: If you need assistance with creating the DNS entries, create a case and request assistance.
Set up custom authentication
- Identify the sending domains you are going to use for your email messages sent through Communications Enterprise.
NOTE: The sending domain is the portion to the right of the @ symbol in the “from" email address. For example, in email@example.com, the sending domain is myjob.com.
- Create new DNS entries by following the instructions below, but replace all occurrences of MYNEWDOMAIN.COM with your sending domain. Do this individually for every domain you will use for sending email messages through Communications Enterprise.
NOTE: These DNS entries are internet standard pointers that direct internet traffic to the correct server to handle those requests.
NOTE: Some DNS providers, such as GoDaddy, will append the domain to the end of each entry. If this is the case, do not include the .MYNEWDOMAIN.COM portion of the CNAME records.
DNS Records for Email Domain: MYNEWDOMAIN.COM
SPF Authentication: CNAME Record Entry: Name: send.MYNEWDOMAIN.COM Alias/points to/target: client.rmsend.com
DKIM Authentication: CNAME Record Entry # 1: Name: HLMAE1._domainkey.MYNEWDOMAIN.COM Alias/points to/target: HLMAE1._domainkey.rmsend.com CNAME Record Entry # 2: Name: HLMAE2._domainkey.MYNEWDOMAIN.COM Alias/points to/target: HLMAE2._domainkey.rmsend.com
- Provide those DNS entries to your IT staff so they can update the appropriate Name Server. The Name Server is the server that stores DNS entries and directs internet requests to the correct server.
NOTE: If your company runs internal- and external-facing Name Servers, add the DNS entries to both servers.
- Use Google Dig to verify that the CNAME entries are referring to the correct hostname and results in a successful TXT record. If you are experiencing issues, see CNAME Troubleshooting for DKIM.
- After those updates have been made by your IT staff, create a case (include the domain setup) so that we can verify the DNS entries and complete the setup.
- After we have completed our setup, we notify the team that your account is ready to be used.