A generated suggestion is a starting point for an authorised DNS change, not a guarantee that the checker has identified every sender or the correct authoritative zone.

Review the suggestion

1. Open PD Modules → Deliverability → Needs attention → How to fix for the intended finding.
2. Confirm the domain and read What to do or the suggested Type, Host / name and Value.
3. Review the existing authoritative DNS records and intended sending configuration.
4. Confirm who is authorised to change that zone before publishing anything.

The module generates certain missing-DMARC suggestions from the current recommendation settings. A sending domain’s missing-SPF finding may require a manual sender inventory instead of a generated value. The no-mail classification is heuristic, so do not assume its restrictive SPF suggestion is safe for an unreviewed domain.

Understand the integrated action

Publish this record now can appear when an installed PD DNS module has a matching zone. The confirmation is a real TXT-record addition. It does not establish that the chosen local zone is authoritative, merge an existing policy, or make repeated clicks idempotent.

Multiple installed DNS modules can hold the same name, and the bridge’s module search order can affect selection. Do not use the button without independently checking the target and existing records. A failure can be uncertain if the provider accepted a write before an error was returned; reconcile the zone before retrying.

Verify afterwards

Check the actual DNS record and run a targeted recheck when appropriate. A successfully added record can still be the wrong policy or target. Resolve any ambiguous zone, duplicate policy or unsupported platform result before using the integrated write. This guide describes the review; it does not recommend a universal SPF or DMARC value.

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