Should I change my DKIM records for DKIM2?
Published 9 Jul 2026
Updated 10 Nov 2026
13 min read
Summarize with

Updated on 10 Nov 2026: We clarified DKIM2 DNS guidance, when standby selectors are required, and how to verify DKIM after a change.
No, do not change working DKIM records just because a setup screen, checker, or article mentions DKIM2. The term has two distinct uses. In some provider interfaces, DKIM2 labels a second conventional DKIM selector or provider-managed key slot. In IETF work, DKIM2 names a separate protocol that remains an Internet-Draft. Neither use is a universal instruction to replace existing DKIM TXT or CNAME records.
Change DNS only when the system that signs your mail gives you exact record names and values. The provider must control the matching private key and specify how the selector will be used, including any standby key for future rotation. Publish the public key or CNAME at the exact DNS name it supplies. DNS publication alone does not activate a new signer. In the worst case, it breaks authentication for mail that was already passing.
First determine whether DKIM2 is a label for a second conventional DKIM record or a reference to the IETF protocol. If a provider tells you to add two records, add both. If a checker or draft mentions DKIM2 without a supported setup path from your sending platform, leave DNS alone.
DKIM2 labels and second selectors
DKIM works by adding a signature header to each message. The receiver reads the signing domain and selector from that header, then queries DNS for the public key. The selector is the part that lets one domain publish more than one DKIM key at the same time. A second selector is normal. It is how providers rotate keys, keep backup keys ready, or separate different sending systems.

DKIM verification flow showing how a message's selector leads to its DNS public key.
This is why a field labelled DKIM2 does not automatically mean the DKIM2 protocol. Microsoft 365 uses selector1 and selector2 for conventional DKIM rotation, while some provider setup screens label two records DKIM1 and DKIM2. The names do not change the protocol. The exact host and value supplied for your domain matter.
- No action: A screen merely mentions DKIM2, current mail passes DKIM and DMARC, and the provider has not requested another record.
- Add a record: Your provider gives a second selector with an exact TXT or CNAME value.
- Rotate a key: Your provider or mail server is ready to sign with a new selector.
- Replace nothing: A second DKIM record is usually additive, not a replacement for the first key.
The DKIM2 protocol is still a draft
The IETF DKIM working group has active Internet-Drafts covering the DKIM2 signature format and related deployment work. These drafts are works in progress, not published RFCs or general mailbox-provider requirements. Draft details can change, so domain administrators should wait for supported sender and receiver implementations instead of translating draft text into manual DNS edits.
The proposed protocol adds DKIM2-Signature and Message-Instance header fields. Participating mail systems use them to build a verifiable handling chain, document message changes, bind a delivery hop to SMTP envelope addresses, and reduce replay. A second conventional DKIM selector does none of this by itself.
- Compatible DNS format: The current DNS draft reuses selector._domainkey names and the v=DKIM1 public-key record format. Do not change v=DKIM1 to v=DKIM2; an unsupported version makes the key record unusable.
- Software dependency: Signers and verifiers must implement the new headers and validation behavior; DNS alone cannot enable DKIM2.
- Gradual transition: Draft deployment guidance calls for conventional DKIM and DKIM2 signing together while support remains limited.
- Hosted-service decision: Act only when your provider documents DKIM2 support and supplies account-specific setup instructions.
The DNS draft also defines a separate DKIM2 domain policy record at _domainkey.example.com to control whether subdomains can authenticate a parent domain's From address. It is separate from selector keys and DMARC policy. Publish it only as part of a supported DKIM2 deployment.
Mail infrastructure operators can track the DKIM2 draft and test only with implementations built for the current draft. Hosted email administrators should keep conventional DKIM working until their provider publishes a supported migration path.
DKIM records for common sending providers
The safest answer depends on who signs the message. The DNS record is only the public half of the key setup. The private key lives with Google Workspace, Microsoft 365, an ESP, a SaaS sender, or your own mail server. If the signer is not changed, the receiver never asks for the new selector.

Google Admin console DKIM authentication screen with selector and record generation controls.
|
|
|
|---|---|---|
Admin console selector | Publish generated TXT record | |
selector1 and selector2 | Publish both supplied CNAMEs | |
ESPs | Provider-defined selectors | Add every required record |
SaaS senders | Sender-specific selectors | Use separate key material |
Custom mail | Administrator-defined selectors | Rotate with overlap |
Conventional DKIM selector setup by sending platform.
For Google Workspace, do not invent a DKIM2 record. Google signs with the selector configured in the Admin console. When generating a replacement key, use a new selector so the existing public key remains available. If Google tells you to generate a new record, publish that exact DNS value, wait for it to resolve, and then start authentication. If your existing selector is passing, leave it in place during any transition.
For Microsoft 365, two conventional DKIM selectors are normal. Only one signs at a time; keep the other published for key rotation. Microsoft uses CNAME records so it can rotate the underlying public key without asking you to edit DNS each time. Follow the current values in the tenant portal rather than a generic template. Newer custom domains can receive tenant-specific CNAME targets that differ from older examples, so the portal values for your domain are the source of truth.
For ESPs and SaaS senders, add the DKIM records each sender provides. Do not point a SaaS sender at your Google or Microsoft selector. Each sender needs its own key material and its own signing configuration. A working setup can have many selectors under the same domain, as long as each selector resolves to one usable public-key record. To contribute to a DMARC pass, the signing domain must meet your policy's domain-matching rule: strict mode requires the exact visible From domain, while relaxed mode permits the same organizational domain.
Why provider instructions matter
A DKIM record is not a standalone switch. It has to match the selector in the DKIM-Signature header and the private key used by the signer. Provider instructions matter because they control both sides of that match. The DNS host name, record type, target, key length, selector name, and timing all come from the sending platform.
Change only DNS
- Missing signer: No outgoing server uses the new selector.
- Wrong key: DNS has a public key that matches no private key.
- Broken record: A CNAME or TXT record is added at the wrong host.
Change signer and DNS
- Matched selector: The header and DNS lookup use the same name.
- Matched keys: The public key verifies the private key signature.
- Clean rollout: Old and new selectors overlap long enough for delivery.
Example provider-managed DKIM CNAMEsDNS
s1._domainkey.example.com. CNAME s1-example._domainkey.provider.net. s2._domainkey.example.com. CNAME s2-example._domainkey.provider.net.
That example shows why copying someone else's DKIM2 value is risky. The visible shape is common, but the target belongs to the provider and tenant. Your record value must come from the account that signs your mail. A TXT-based key normally starts with v=DKIM1 and contains the public key in p=, while a CNAME delegates that lookup to the provider.
When to change DKIM DNS
Use the provider and signer state to decide how urgent the DNS change is.
Leave unchanged
No DNS edit
Current mail passes DKIM, no required record is missing, and no key change is scheduled.
Add only
Publish new record
Provider gives a second selector for verification or rotation.
Rotate
Overlap keys
Signer is ready to use a new selector after DNS resolves.
Emergency
Revoke and monitor
A private key was exposed or an unauthorized signer is active.
Risks of replacing an active DKIM selector
The main risk is replacing a valid selector before the new one is actually used. Receivers verify the selector named in the message header. If you remove or overwrite the old DNS record, signatures using that selector fail once receivers no longer have the matching public key cached. This also affects messages already waiting in delivery queues.
Do not overwrite an existing DKIM TXT record with a DKIM2 value unless the provider explicitly says that exact selector is being replaced. Most safe rollouts add a new selector, verify DNS, switch signing, then retain the old public key until previously signed mail has cleared delivery queues. Follow your provider's documented overlap period.
Broken DKIM does not always break DMARC by itself if SPF passes for an envelope-sender domain that meets the DMARC domain-matching rule. That is not a reason to accept the break. Many real sending paths rely on DKIM domain matching because forwarding often breaks SPF. If your DKIM fails after a DNS edit, forwarded mail and SaaS mail can lose the only matching authentication result available to DMARC.
- Authentication failures: Receivers cannot verify signatures tied to the old selector.
- DMARC damage: Messages fail DMARC when no passing DKIM signature or SPF result meets the required domain-matching rule.
- DNS conflicts: A host cannot have both CNAME and TXT records at the same name. Publishing two different DKIM public-key TXT records at one selector also causes verification errors; use separate selectors instead.
- Slow recovery: Cached DNS answers keep bad values alive after you fix them.
Key changes also affect investigation work. When selectors change without documentation, it becomes harder to tell which system signed which messages. That matters during incident response, vendor cleanup, and DMARC policy staging. When you control the mail infrastructure, keep selector names simple, dated, and tied to the sending system.
How to verify DKIM before and after a change
Start with a real message sent through the system in question to an external mailbox. For conventional DKIM, inspect the DKIM-Signature header and write down its d= signing domain and s= selector, then check DNS for that exact selector. A value such as s=selector2 is still conventional DKIM. Actual DKIM2 test mail uses DKIM2-Signature and Message-Instance header fields, which require compatible signing and verification software.
Map a conventional DKIM header excerpt to its DNS keytext
DKIM-Signature: v=1; a=rsa-sha256; d=example.com; s=selector2; ... DNS lookup: selector2._domainkey.example.com TXT
A DNS lookup confirms that a public key is published. It cannot verify whether an outgoing message was signed correctly. After enabling or rotating signing, check the receiving system's Authentication-Results header for dkim=pass and confirm the expected signing domain and selector. Check dmarc=pass separately, because SPF alone can make DMARC pass while DKIM is broken.

DKIM checker sample results showing selector, DKIM DNS record, validation checks, parameters, and share link
Suped's DKIM checker is useful when you know the selector. It shows whether the DNS value parses correctly, whether the key is present, and whether obvious formatting problems exist. Suped's broader domain health check helps when you are not sure whether the issue is DKIM, SPF, DMARC, or DNS.
DKIM checker
Check selector records and public key configuration.
?/7tests passed
Suped is our DMARC reporting and email authentication platform. Its DMARC monitoring workflow groups reported authentication results by sending source so you can compare DKIM and DMARC failures before and after a change. Use message headers for immediate confirmation, then review incoming aggregate reports for wider traffic coverage. Not every receiver sends reports.

DKIM2 DNS change decision: check provider instructions, publish the supplied selector, then test DKIM and monitor DMARC.
When to rotate or replace DKIM keys
A DKIM change is appropriate when the sending platform supplies a supported rollout plan. The word DKIM2 alone is not a reason to edit DNS.
Illustrative custom DKIM rotation with an abbreviated public keyDNS
202607._domainkey.example.com. TXT "v=DKIM1; k=rsa; p=MIIB..."
For custom mail infrastructure, generate a new key pair and publish its public key under a new selector. For RSA, use at least 2048 bits where supported; changing key length is separate from adopting DKIM2. Allow DNS propagation, including cached missing-record answers, before switching the signer. Send tests, then retain the old public key through your system's maximum delivery retry period. DNS TTL alone does not tell you when old signed mail has finished delivery. If you are evaluating DKIM2 deployment work at the mail-server layer, the milter rollout path is relevant. For normal hosted email administration, it is not a reason to hand-edit DNS early.
- New sender: Add the DKIM record for a new ESP, SaaS tool, or mail gateway.
- Key rotation: Publish the new selector before switching signing.
- Compromised key: Stop the affected signer and revoke the exposed key promptly; do not wait for routine rotation. Use an empty p= value for a TXT key, or the provider's revocation process for a managed key.
- Provider migration: Run old and new selectors together during the cutover.
Selector changes deserve the same care as any other authentication change. They are small DNS edits with large delivery consequences. If you rotate selectors often, document the owner, date, provider, and signing system for each selector so future checks do not turn into guesswork. More detail on operational rotation is covered in selector rotation.
Decision checklist
Use this checklist before touching DNS. It keeps the decision tied to the sender that actually signs mail instead of a label shown by a checker or setup screen.
- Current mail passes: Leave working records unchanged unless your provider requires another selector or a key needs rotation or revocation.
- Provider gave values: Publish the exact selector TXT or CNAME record from the signing provider.
- Signer is ready: Change signing only after the new DNS record resolves correctly.
- Old key still needed: Keep the old public key until previously signed mail has cleared delivery queues, except when the key is compromised.
- No exact instruction: Do not create, rename, or overwrite records based on a DKIM2 label or draft alone.
- After the change: Send test mail, inspect headers, and monitor DMARC results for failures.
Frequently asked questions
No. When DKIM2 is a provider label, it usually means a second selector or key. The IETF DKIM2 protocol also reuses the existing DKIM key-record format in its current draft. Do not replace a working selector unless your provider says that exact selector is being retired.
Yes, when DKIM1 and DKIM2 are provider labels for separate conventional selectors. Each selector has its own DNS name. For the actual IETF protocol, naming a selector DKIM2 does not enable DKIM2; compatible signing software must add the new header fields.
Microsoft 365 uses two selector CNAME records so Microsoft can manage conventional DKIM key rotation behind those records. Normally, only one selector signs at a time. Publish the CNAMEs shown for your domain in the tenant portal, then enable DKIM after both records verify.
Check whether any live conventional DKIM message uses that value as its selector and whether your provider requires the record. A required standby selector still needs publishing even when no test message uses it yet. If neither condition applies, the missing DKIM2 label is not an immediate problem. Actual DKIM2 protocol support must be confirmed in your sending software, not inferred from a DNS lookup.
No. DMARC passes when SPF or conventional DKIM passes with the required match to the visible From domain. Current DKIM2 Internet-Drafts do not make DKIM2 a DMARC requirement. Keep the DKIM selector used by your real mail resolvable and valid.

