Deliverability "Check now" can report stale DNS data #385

Closed
opened 2026-11-13 13:49:23 +00:00 by StefanSa · 1 comment

Summary

A manually requested Deliverability Check now can still use stale DNS data from the server's normal DNS caches.

This can make a newly generated report show outdated PTR, DMARC or other DNS information even though the public DNS has already been corrected.

The scheduled daily check should keep its current cached behaviour, but an explicit Check now should use fresh DNS results.

Problem

Check now creates a new Deliverability report, but the DNS lookups behind that report currently reuse the same cached DNS data as normal server operation.

This includes PTR, A/AAAA, TXT, MX and the DNS lookups used by SPF and DKIM verification.

As a result, a manual check can report an old state until the internal DNS cache expires.

For example:

  • reverse DNS has already been changed to match the SMTP EHLO name
  • a valid DMARC record is already present in public DNS

but a new Deliverability report can still show the previous PTR and report DMARC as missing.

That is unexpected for an operation explicitly called Check now.

Proposed change

For manually requested Deliverability checks, use uncached resolver lookups for the DNS-backed checks.

Scheduled checks should continue to use the existing caches.

The change should not:

  • flush or modify the shared DNS caches
  • change DNS behaviour for normal SMTP delivery
  • change the existing manual-check rate limit

I have attached a patch implementing this approach.

Validation

The patch has been tested against v2026.11.11.

Results:

  • manual checks select fresh DNS lookups
  • scheduled checks retain cached lookups
  • SPF and DKIM follow the selected lookup mode
  • the existing manual-check rate limit remains unchanged
  • focused Deliverability service tests pass
  • focused Deliverability integration test passes
  • formatting and diff checks pass

I did not perform the optional production rollout test; the patch was validated through the focused service and integration tests.

Best regards
Stefan

## Summary A manually requested Deliverability **Check now** can still use stale DNS data from the server's normal DNS caches. This can make a newly generated report show outdated PTR, DMARC or other DNS information even though the public DNS has already been corrected. The scheduled daily check should keep its current cached behaviour, but an explicit **Check now** should use fresh DNS results. ## Problem `Check now` creates a new Deliverability report, but the DNS lookups behind that report currently reuse the same cached DNS data as normal server operation. This includes PTR, A/AAAA, TXT, MX and the DNS lookups used by SPF and DKIM verification. As a result, a manual check can report an old state until the internal DNS cache expires. For example: - reverse DNS has already been changed to match the SMTP EHLO name - a valid DMARC record is already present in public DNS but a new Deliverability report can still show the previous PTR and report DMARC as missing. That is unexpected for an operation explicitly called **Check now**. ## Proposed change For manually requested Deliverability checks, use uncached resolver lookups for the DNS-backed checks. Scheduled checks should continue to use the existing caches. The change should not: - flush or modify the shared DNS caches - change DNS behaviour for normal SMTP delivery - change the existing manual-check rate limit I have attached a patch implementing this approach. ## Validation The patch has been tested against `v2026.11.11`. Results: - manual checks select fresh DNS lookups - scheduled checks retain cached lookups - SPF and DKIM follow the selected lookup mode - the existing manual-check rate limit remains unchanged - focused Deliverability service tests pass - focused Deliverability integration test passes - formatting and diff checks pass I did not perform the optional production rollout test; the patch was validated through the focused service and integration tests. Best regards Stefan
jcoffey-dev added the bug
priority
p2
labels 2026-11-13 14:02:33 +00:00
jcoffey-dev self-assigned this 2026-11-13 14:02:33 +00:00
Owner

Thanks @StefanSa, nice patch. It's in #387 with you as the author. It needed one small rebase: main had already dropped the unused VerifyPolicy import. The unit tests and deliverability_tests pass here on main.

One note for anyone else reading: this skips inbuxa's own DNS caches. A caching resolver in front of the server (systemd-resolved, Unbound and so on) can still hand back an old answer until its own TTL runs out.

It'll be in the next release.

Thanks @StefanSa, nice patch. It's in #387 with you as the author. It needed one small rebase: main had already dropped the unused `VerifyPolicy` import. The unit tests and `deliverability_tests` pass here on main. One note for anyone else reading: this skips inbuxa's own DNS caches. A caching resolver in front of the server (systemd-resolved, Unbound and so on) can still hand back an old answer until its own TTL runs out. It'll be in the next release.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: inbuxa/inbuxa-server#385