Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
19
-
Description
Is there any option for you to add a CNAME or other alias for your DKIM DNS names? They conflict with another prominent remailing service’s entry. Having many customers establish mailing subdomains to get mail sent from your system to deliver properly seems much more intrusive than having an alternate name set to offer to solve this issue.
Basically, What I am asking is if you would consider adding an alias to the existing record providing 2 options for what a customer can set in their DKIM DNS entries to point to to validate the signature. Ideally, if you added something like s3._domainkey.atlassian.net CNAME to s1._domainkey.atlassian.net and s4 to s2. That should resolve the existing conflict with sendgrid entries that are required to properly deliver Pagerduty and other service emails. Maybe that change would break validation in the DKIM verification chain but it doesn’t seem like it would. It should also not affect anyone using current settings or configurations