TXT record splitting for DKIM: one record can contain several strings

Define the decision

Long public keys may be represented as multiple quoted strings in DNS output. That presentation can be valid within one record. Splitting a key into separate records or inserting extra characters can make the selector unusable.

Work through the procedure

1. Obtain the exact public value from the sending provider.
2. Check how your DNS editor accepts long TXT values.
3. Query the selector and inspect record boundaries, not just visual line wrapping.
4. Verify a fresh signed message after publication.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Conceptual valid shape: one TXT record containing "first-part" "second-part"
Different shape: two separate TXT records, each holding half the key
Verification target: one complete public-key value reconstructed by the lookup

Read the result

The example describes record structure; it is not a usable public key. When a dashboard adds quotes automatically, copying displayed quotes back into the value may introduce unintended data.

Check before moving on

1. Compare the reconstructed value with the provider’s value.
2. Check that the selector name and record type are also correct.

Limits and next action

Use provider-supported DNS entry instructions rather than editing cryptographic material manually. If the provider requires CNAME delegation, do not replace it with a guessed TXT key.

Source: RFC 6376: TXT key record representation