Use a targeted recheck to inspect the DNS observation for an existing finding after an authorised correction. Keep the DNS result separate from successful message authentication or delivery.

Recheck the affected domain

1. Open PD Modules → Deliverability → Needs attention.
2. Find the relevant row and choose How to fix.
3. Confirm the domain and finding before choosing Check this domain now.
4. Read the outcome, then review the resulting grade and other findings.

This targets the domain associated with the selected finding. The general Check now button instead runs a synchronised batch; it is not a targeted refresh of whichever row you happened to be viewing.

Interpret the message carefully

The targeted action can report a finding closed when the latest grading no longer produces that kind. It can do this after a lookup problem or a classification change, not only after the intended record becomes correct. The action’s success message alone is not proof that the DNS fix worked.

An apex TXT failure is partly distinguished from absence, but failed DMARC or selector lookups can still be interpreted as missing records. Check the exact DNS observation and any lookup note before publishing a replacement for something that may already exist.

If the finding remains

Review the authoritative zone, queried name, record type, current published value and relevant caching. A remaining finding can reflect a real configuration issue or incomplete checker support; it is not always just propagation delay. Avoid repeated blind writes or rechecks.

Omit private mail contents and credentials. Do not delete findings to simulate a successful correction.

See the PD Email Deliverability Blesta guide for related tasks, or explore PD Email Deliverability.