Email, Configuring Authenticated Email using a vendor DKIM record
This KB provides the steps necessary to set up custom domain authentication for 3rd party and cloud applications
Setting up Custom Domain Authentication: DKIM and SPF (using SendGrid)
This KB provides the steps necessary to set up custom domain authentication for areas on campus that use SendGrid for some of their emailing needs.
To improve deliverability of emails sent by SendGrid SPF and DKIM have to be configured. In this article, you'll learn how to set up DKIM and add SendGrid to your SPF record.
Before You Start
Here are some things to know before you begin this process.
When you set up an authenticated domain, you will be given the option of using automated or manual security. When you select automated security, SendGrid will manage your DKIM and SPF records for you. This means that whenever you make a change to your account that could impact your deliverability, such as adding a new dedicated sending IP address, SendGrid will automatically update your DNS settings and your DKIM signature.
To set up domain authentication, you must submit the DNS records provided by SendGrid to your DNS or your domain record with the campus host manager. The CNAME record creates an alias for subdomain.yourdomain.com and points to sendgrid.net. This will be what your messages are signed by, so your recipients will be able to see what you have chosen for your CNAME. You set up the CNAME files that SendGrid provides with your DNS host.
Here's a brief overview of the process.
In Your Domain Record
or Zone Editor
In the SendGrid UI, select Settings > Sender Authentication.
In the domain authentication section, add in information about your DNS host, and indicate whether you also want to set up link branding. For more information about link branding, check What is link branding?.
Fill in the domain that you want to send from (illinois.edu or subdomain.illinois.edu) For more information about advanced settings, see Advanced settings.
Next, you need to add all of the CNAME records in the next column to your DNS host. This process varies depending on your DNS host.
Example DKIM Record: Automated Security ON
subdomain.yourdomain.com. | CNAME | uXXXXXXX.wlXXX.sendgrid.net
s1._domainkey.yourdomain.com. | CNAME | s1._domainkey.uXXX.wlXXX.sendgrid.net.
s2._domainkey.yourdomain.com. | CNAME | s2._domainkey.uXXX.wlXXX.sendgrid.net.
For help with this: https://sendgrid.com/docs/glossary/dkim/
If you do not want to use a subdomain, contact firstname.lastname@example.org.
Update your SPF record to allow Sendgrid to send emails on your behalf.
For help with this: https://sendgrid.com/docs/glossary/spf/
DONE - Create a TXT record for subdomain.illinois.edu with this value: v=spf1 include:sendgrid.net ~all
NOTE: if you intend to send email ‘as’ @illinois.edu, we cannot add additional include statements to the campus SPF record. This will require that the vendor use their own domain in the ‘mail from’ address of messages, while using ‘illinois.edu’ in the ‘header from’, using the DKIM signature coordinated with Technology Services in the prior step.