Configurator Direct NS check fails for long public key

[NormHenderson]

Versions

• Windows Server Version: 2019
• Exchange Version: 2019
• Installed DKIM Exchange Version: 3.3.1

Description

My DKIM setup appears to work fine (messages sent to Office365 receive a DKIM pass). Because the public key and more specifically the DKIM DNS record is longer than 256 bytes, the DNS server (he.net) automatically divides it into two parts. dig -t TXT 1._domainkey.domain.name returns both parts correctly.

When running Configuration.DkimSigner.exe, Domain Settings, the suggested DNS record contains the correct public key. However when selecting "Direct NS Check", only the first part of the key is retrieved from the DNS server and appears in the box, and the tool reports a failure.

Steps to Reproduce

1. Add a domain and generate a 2048-bit key pair using Configuration.DkimSigner. The public key will be 398 bytes.
2. Publish the suggested DNS record.
3. After propagation time, do a Direct NS Check in Configuration.DkimSigner.

Expected behavior: [What you expected to happen] Check should succeed and the full DKIM DNS record should be shown in the box.

Actual behavior: [What actually happened] Check fails and in the box, only the first 256 characters of the DNS record appear.

[soosp]

You should break the key to more lines in the input field of the DNS SnapIn. It works for me. A suggestion to the developers: It would be fine to add a checkbox for adding line breaks for the Suggested DNS record.