This is the TXT record SM want me to create:
Record name: 8DBA8A503B29CA2._domainKey
Record value: v=DKIM1; k=rsa; h=sha256; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD2xQYKyM1+4T/Dr/sx/HgnEA4UFBWdRESxdsegfR7RbuZkWwn5ONC27Xe+RE3lnMkpkfWFvUHgEJmAD6gxchhZyMjZzOtu+KUDgP8se1SlWp129YRq/h4VJOaFECmxdl71dIeqXt6JsyVx2UO+GCbOmSXan0iFja+9MQJANxWkgwIDAQAB
And this is the record that I've created: 8DBA892D3004272._domainkey.lambda.hr
I can check the record via any online DNS tool and confirm that it's added corrently.
> dig 8.8.8.8 8DBA892D3004272._domainkey.lambda.hr TXT +short
"v=DKIM1; k=rsa; h=sha256; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD2xQYKyM1+4T/Dr/sx/HgnEA4UFBWdRESxdsegfR7RbuZkWwn5ONC27Xe+RE3lnMkpkfWFvUHgEJmAD6gxchhZyMjZzOtu+KUDgP8se1SlWp129YRq/h4VJOaFECmxdl71dIeqXt6JsyVx2UO+GCbOmSXan0iFja+9MQJANxWkgwIDAQAB"
Why doesn't SM see the record ? SM is configured to use 8.8.8.8 and 1.1.1.1 for DNS. When I check the record with nslookoup or dig I can see it's there and looks exactly the same as the one above.
I've tried restarting the whole server (in an effort to purge any caches) but nothing helps.
The domain I'm trying to active DKIM on is, obviously, "lambda.hr".