Invalid DNS value

[happy22]

user unable to enter long string in TXT dns record for DKIM key.

 

[Zhenyapan]

you can divide it to parts separated with doublequotes
"code1""code2""code3"

 

[Zhenyapan]

here how it looks inside DNS .db file

 

[happy22]

thanks but no matter where the user puts the quotes or how many times he splits it, the field remains 'invalid'

 

[happy22]

this dns entry with long string was accepted without splitting. but user cannot add new long string TXT records

 

[Richard G]

but user cannot add new long string TXT records

Yes he can, but then he should not work with old style keys, but use modern key.

Look at your key and the key from the user. Your key starts correctly with:
"v=DKIM1; k=rsa; p=therest"

Now your user's key says:
"v=DKIM1; k=sha256; p=therest"

Use SHA-256. Originally, DKIM also supported SHA-1. This is no longer allowed due to cryptographic weaknesses in SHA-1.

So your user needs to create a new DKIM key with RSA.

 

[happy22]

Hi, the key is using RSA already. The "h=sha256" refers to the hashing scheme employed for securing emails, which is also a standard practice across the industry. Most providers use this hashing scheme due to its reliability and security.
so why cant user use this key with DA? - seems like some validation rule is being wrongly applied on the field

 

[happy22]

he's trying to enter this key and get invalid

v=DKIM1;h=sha256;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAprCXzeZcp6MNwD4HiM2duBQjlOKyjAS27e4TW9gKlrmMZepxdr9jW24E1v9n9ZeHdqqh0+BPdWdVQHtrbRmB+K4SpVbEOfrlmsuibfLyxJ/56kVnEVR5gyDnDEY7spDLvPcfXTM7b4G7wf2/suZkqoQYLhfKscorL21TSmvTzLzeSMFTrp8VL+48fS9p6388SS29jBA8943MeXHsN8Er2SuaPbSTJ7BKXpH1UZvHKtE0+4JYuId93r/7FY7rCMlYyYGDe1PhEAjQKFyWZUYrqmYUfsoBRL/MPDD3p/MNaMNYYaMLf8BugJmBuf1mO+Dc/h6Wx6qMHPjJRtjYn3yZmQIDAQAB

 

[happy22]

same key can be entered to cloudflare without issues and appears in mxtoolbox

 

[Richard G]

Normally DA has no issues with long keys so that is odd. Normally one can also use multiple lines.
I would suggest sending in a ticket then. Might be a DA issue.