How to implement DKIM without a TXT record?
Summary
What email marketers say8Marketer opinions
Email marketer from Reddit shares that using a CNAME record for DKIM is a common practice when you want to delegate the management of your DKIM key to a third-party service. This allows the service to rotate the key without you needing to update your DNS records directly.
Email marketer from MXToolbox describes setting up DKIM with a CNAME record pointing to a service like SendGrid or Mailgun, which handles the TXT record. They also mention that this simplifies DKIM management, especially for larger organizations
Email marketer from StackExchange explains that you can create a CNAME record in your DNS that points to another domain. Then you can put the DKIM TXT record on that other domain. This allows you to update the DKIM key on the other domain without having to change the DNS records on your primary domain.
Email marketer from AuthSMTP explains how DKIM CNAME is the best option as you are not managing the DKIM keys directly. This is required when you use AuthSMTP.
Marketer from Email Geeks answers you can do DKIM without a TXT record via CNAME.
Email marketer from Mailgun's documentation shares that DKIM is implemented by creating CNAME records in DNS. Mailgun then hosts the TXT record for DKIM. They also say the CNAME method is best practice as it simplifies DKIM management.
Email marketer from StackOverflow explains using CNAMEs for DKIM records allows an external service to manage the DKIM key. This is done by creating a CNAME record pointing to the service's domain which hosts the actual DKIM TXT record, allowing easier key rotation and management by the service provider.
Email marketer from SuperUser shares their experience using CNAME records for DKIM delegation, finding it simplified their DKIM management process. They emphasize the importance of ensuring the CNAME target is correctly configured and maintained by the delegated service.
What the experts say4Expert opinions
Marketer from Email Geeks answers you can do DKIM without a TXT record using CNAME.
Expert from Spam Resource explains that to implement DKIM using a CNAME record, you create a CNAME record that points to the domain where the actual DKIM TXT record is hosted. This is often used when delegating DKIM management to a third-party email service provider.
Expert from Email Geeks answers you can do DKIM without a TXT record using CNAME.
Expert from Word to the Wise explains using CNAMEs in DKIM allows delegation of signing to a different host. They also mention it can be used with services where you don't want them to have full access to your root domain. However, they advise ensuring all your subdomains also have DKIM records.
What the documentation says4Technical articles
Documentation from SendGrid explains that to implement DKIM with SendGrid, users create CNAME records in their DNS settings that point to SendGrid's servers. SendGrid then manages the actual DKIM key and rotates it automatically, simplifying the process for the user.
Documentation from RFC Editor explains that DKIM (DomainKeys Identified Mail) allows for DNS CNAME records to be used for DKIM keys. The selector record can point to another domain where the TXT record is stored, using a CNAME.
Documentation from Google Workspace Admin Help states that using CNAME records for DKIM is a supported method for delegating DKIM management to services like SendGrid. It outlines the steps for creating a CNAME record that points to the service's DKIM record.
Documentation from Cloudflare clarifies that CNAME records are valid for DKIM, especially when using a third-party email service. The CNAME points to the third-party's domain, where they manage the DKIM TXT record. This simplifies DKIM key rotation.