## TL;DR
Treat temperror as a DNS health problem, not a sender problem: the verifier could not fetch the DKIM public key in time, so the verdict was deferred. Check the resolver your mail gateway uses, look for timeouts and SERVFAIL responses on selector lookups during the affected window, fix forwarding or resolver overload, and confirm the same senders verify cleanly once lookups succeed consistently.

```text
"dkim=temperror" dns timeout when verifying inbound mail
```

## Use this when
- Authentication-Results show dkim=temperror for multiple unrelated senders in the same window.
- Retried or later mail from the same senders passes DKIM.
- The gateway or its upstream resolver logged DNS timeouts at the same time.

## Not for this skill when
- One sender always fails with dkim=fail or none. That is a key or signing problem at that sender.
- All DNS is down and mail is deferring generally. Fix the outage first, then recheck DKIM.

## Steps
1. Gather several temperror samples and note the senders, selectors, and timestamps to prove the pattern is time based, not sender based. Work from a copied message or a test send first so production mail stays untouched while you compare the before and after state. Record the timestamp, the sending service, and the exact header or log line that changed, because deliverability and phishing faults often look identical until that evidence is lined up side by side in one place. Verify: samples span multiple senders inside one time window
2. Query the same selector records from the gateway host using its configured resolver and time the responses. Do not change more than one setting at a time here. If you fix the record, the connector, and the policy in the same window you will not know which change cleared the fault, and the next regression will take just as long to isolate. Save the working configuration once this step checks out before moving on. Verify: a slow, timed out, or SERVFAIL lookup is reproduced from the gateway
3. Check resolver health: upstream forwarder latency, local cache load, and any DNS filtering service in the path. Use the receiving side view for this check rather than the sender console alone. Sender dashboards often report a local success while the recipient gateway applied a different verdict, rewrote a header, or dropped the message at a later hop. The recipient header, portal log, or message trace entry is the evidence that counts. Verify: the slow hop in the lookup chain is identified
4. Fix the resolver path, by pointing the gateway at a healthy resolver, repairing the forwarder, or raising the lookup timeout within sane limits. Keep any exception you create narrow and time boxed. Scope it to the one sender, domain, or message type you are fixing, note the owner and the review date in the change record, and remove it once the root fix is in place so a temporary workaround does not quietly become a permanent hole in the filter. Verify: repeated selector lookups return quickly and consistently
5. Monitor Authentication-Results on inbound mail for the next day. Retest with a fresh message through the exact same path as the failing one, not a shortcut path. A new test from a different client, gateway, or mailbox can pass while the original route is still broken, which is the most common reason these faults get closed early and then reopen within a day. Verify: dkim=temperror entries stop and the same senders show pass verdicts

## Why it happens
DKIM verification needs a live DNS lookup for every signing selector. When that lookup times out, verifiers must not call the signature bad, so they record a temporary error and usually accept the message on other signals. Intermittent resolver trouble, an overloaded local cache, or a filtering DNS service throttling queries all produce bursts of temperror that resolve themselves, which is why the pattern is time correlated across senders.

## Variants and edge cases
### dkim temperror dns timeout verifying inbound mail intermittent
The intermittency phrasing that separates this from a hard fail.
### dkim=temperror multiple senders resolver problem gateway
The multi-sender variant that points at local DNS.
### authentication results temperror instead of pass exchange google
The header-reading variant used from delivered mail.

Compatibility: RFC 6376 DKIM, Exchange Online Protection and Google Workspace inbound verification, BIND, Unbound, and forwarded resolver setups.

Edge cases to check:
- A temperror burst during a real DNS outage is expected; the fault to fix is any burst with no matching resolver event.
- Large DKIM keys and long TXT records make lookups slower and more likely to hit UDP size or timeout edges.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_GkwXqB1OSpoPmnESXcvQUg