custom dkim selector name
It's a shame you are obliged to have a DKIM selector (key) name of 'default', and there is no ability to rotate keys as once you update the 'dafault' key will change value, meaning messages sent under the prior key, also called 'default', will fail.
GMail offers a nice option where you specify the selector name and so can rotate keys nicely. O365 has a more basis scheme were keys have to be called selevtor1 and selector2 (from memory), flip-flopping between the two. Not elegant.
Gmail is the way to go...
- Enable DKIM
- What would you like your Selector (key) name to be?
- Key used and public key published to local DNS OR returned to UI with instruction to; "Create NS record looking like..."
Iain
shared this idea
-
SilvioK
commented
>We have another platform that also uses "default"<
Same here. -
J Anything
commented
Any update on this? It's a bad design to not allow this to be changed. We have another platform that also uses "default" and cannot be changed. So now we're stuck.
-
GB
commented
We need this too. At Gmail we can set the selector to ‘2019052200’ so that a new key is immediately available in the dns. When the selector is always ‘default’ the new key depends heavily on local dns TTLs and stale caches.