Security Policy Errors

Fix DKIM CnameMissing Errors in Office 365 GCC

Kushani NimanthikaKushani Nimanthika Nov 13, 2026 869 views

Question details

Identify why DKIM remains in the CnameMissing state for a custom domain in an Office 365 GCC tenant.

Fix DKIM CnameMissing Errors in Office 365 GCC
Product
Microsoft 365 GCC
Device & OS
not provided
Scenario
An administrator wants to enable DKIM signing for a custom email domain after adding DNS selector records.
Observed behavior
Microsoft 365 reports CnameMissing even though the DKIM selector records appear to resolve.
Before you start

Have administrator access to the Microsoft 365 Defender portal and the public DNS provider for the affected domain. Identify the custom domain and the DKIM CNAME targets shown for it in your GCC tenant.

Solution 1Recommended

Verify Both DKIM Selector CNAME Records in Public DNS

Use this method when Microsoft 365 reports CnameMissing despite apparent DNS resolution.

1
Find the required targets

In the Microsoft 365 Defender portal, open Email & collaboration > Policies & rules > Threat policies > DKIM. Select the affected custom domain and review the CNAME names and targets shown for it.

2
Check both DNS records

In your public DNS provider's management console, confirm that both selector1._domainkey and selector2._domainkey are CNAME records for the custom domain. Compare each target with the exact value shown in the portal; do not assume targets from another tenant or cloud environment apply.

3
Correct record names and values

Edit any incorrect records in the DNS provider's console. Check whether the provider automatically appends the domain name to the host field, and remove any conflicting records at the same selector names.

4
Query authoritative DNS

Run `nslookup -type=NS example.com` to find the domain's authoritative name servers. Then query each selector against an authoritative server, for example `nslookup -type=CNAME selector1._domainkey.example.com ns1.example.net`, and repeat for selector2. Replace the example names with your domain and an actual authoritative server.

5
Enable DKIM signing

After both public records return the expected targets and DNS changes have propagated, return to the domain's DKIM settings in Microsoft 365 Defender and enable signing.

Verify Both DKIM Selector CNAME Records in Public DNS
Allow time for DNS changes: DNS caches can continue to return older results until their TTL expires. Setting a TTL of 3600 seconds may help manage future changes, but it does not immediately clear existing cached responses.
Free Microsoft Office alternative

Work with Office Files in WPS Office

WPS Office is a free, lightweight alternative with a familiar interface and Microsoft Office format compatibility for a smooth move between office suites. It does not manage Microsoft 365 GCC DNS or fix DKIM errors.

Use a free, lightweight office suite with a familiar interfaceOpen and edit Microsoft Word, Excel, and PowerPoint formatsDocument DKIM troubleshooting checks in a spreadsheet or documentMove existing Office files into a familiar workflow
microsoft office alternative - wps office

Frequently Asked Questions

Why does Microsoft 365 show CnameMissing when one selector resolves?

DKIM requires both selector CNAME records for the custom domain. Check selector1._domainkey and selector2._domainkey in public DNS and compare their targets with the values shown in the Microsoft 365 Defender DKIM settings.

Where can I find the correct CNAME targets for my GCC domain?

Open the DKIM page under Email & collaboration > Policies & rules > Threat policies in the Microsoft 365 Defender portal, and select the custom domain. Use the targets displayed for that domain rather than copying values from another tenant.

How can I check whether the authoritative DNS servers have the records?

Use `nslookup -type=NS` with your domain to find its authoritative name servers. Then run `nslookup -type=CNAME` for each selector, specifying one of those servers, and compare the returned targets with the portal.

Will changing the DNS TTL immediately resolve CnameMissing?

No. A shorter TTL can affect how long future responses are cached, but existing cached responses may remain until their previous TTL expires. Wait for propagation and check both selectors again.