Use PD AWS Route 53 DNS to publish the email authentication records supplied by your mail administrator or provider. SPF, DKIM and DMARC have different hostnames and purposes; a correct DNS value is only part of a working mail configuration.

Collect the intended records

Obtain your domain’s SPF policy, DKIM selector/value or CNAME targets, and the chosen DMARC policy. Identify every authorised sending service before revising an existing SPF policy. Do not copy another customer’s selector or tenant target.

Open the authoritative Route 53 zone’s records in the module. Customers can use the configured DNS Manager navigation link or Manage DNS on a linked domain/service. A same-named hosted zone that the registrar does not delegate to will not supply public answers.

Publish by the requested type

1. Search for existing records at each requested hostname.
2. For SPF, choose TXT and enter the intended complete policy at the requested name.
3. For DKIM, use the provider’s exact selector hostname and its requested TXT or CNAME type.
4. For DMARC, use TXT at the requested DMARC name with the agreed policy.
5. Save each record, then reload and compare names, types and values.

Keep one intended SPF policy at a hostname; publishing a second policy is not a way to add a sender. DKIM’s selector belongs in the name. A DMARC enforcement change should reflect the mail administrator’s plan rather than a quick response to a warning.

Verify DNS and messages separately

Check the authoritative records and provider validation, then inspect the authentication results on a controlled message. Publishing DNS does not configure DKIM signing in the mail service or promise inbox placement. MX delivery destinations are a separate mail-routing task.

If a save is refused, retain the exact redacted error and inspect the policy, quota, lock or AWS action involved. If DNS is correct but authentication fails, compare the actual message’s sender domain and selector with the published records instead of repeatedly replacing working TXT values.

Check same-named hosted zones before changes

If your AWS account contains multiple hosted zones with the same domain name, do not assume choosing a same-named row selects a particular hosted-zone ID. This module resolves zones by name. Have your AWS administrator compare the exact hosted-zone ID, records and delegated nameservers before using module writes; use AWS’s native zone-specific controls if the target remains ambiguous. Do not create or delete another zone to diagnose that ambiguity.

See the PD AWS Route 53 DNS WHMCS guide for related tasks, or explore the module.