Publish the TXT record requested by a service to verify control of your domain. PD AWS Route 53 DNS stores the requested DNS value at the provider; the requesting service decides whether verification has passed.

Check the latest request

Keep the record type, complete requested hostname and latest value from the service. An apex record differs from one beneath a verification label. Do not repeat the domain suffix accidentally when entering a full name.

Open the zone’s records through AWS Route 53 DNS → Zones, or use My Tools in the client portal, then the DNS manager as the customer. Confirm that the public domain delegates to this specific hosted zone, especially if more than one zone has the same name.

Save the TXT value

1. Search for existing TXT records at the intended name.
2. Select TXT in the record editor.
3. Enter the correct name, TTL and complete content.
4. Save without removing unrelated values such as SPF or other verifications.
5. Reload and compare the saved result with the latest service request.
6. Run the requesting service’s verification check after confirming the public DNS value.

Multiple TXT values at a name can be legitimate. Edit the intended value rather than replacing an entire record set indiscriminately. The module handles Route 53 TXT presentation; keep the actual requested value intact rather than shortening a long verification string.

Diagnose a failed verification

Separate a refused save from a successfully saved record that the service cannot see. The first can concern permissions, policy, lock or quota. The second can concern a wrong name, a different authoritative zone, stale caches or a new value issued by the service.

Do not clear other verification or mail records to make a single checker pass. Keep account-specific values out of public support screenshots where they are unnecessary. Once verified, follow the service’s retention instructions rather than automatically deleting the record. See the mail authentication guide for TXT records used by email services.

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 Blesta guide for related tasks, or explore the module.