Many services ask you to publish a TXT value to prove control of a domain. Add the exact record requested through PD Cloudflare DNS, then complete verification in the requesting service.

Copy the requested details

Obtain the record Type, Name/Host, Content/Value and any TTL guidance from the service being verified. Keep its requested hostname separate from the token value. An account-specific verification value should not be invented or taken from another account’s example.

Add the TXT record

1. Open the correct zone through the enabled DNS Manager client-navigation link, or Manage DNS on the linked domain/service, or Cloudflare DNS → Zones → Records as staff.
2. Search for the requested name and inspect existing TXT records.
3. Choose Add record → TXT.
4. Enter the requested name, using @ only when the request is for the zone root.
5. Paste the complete content into the TXT value field and select the intended TTL.
6. Save and confirm the final full record name and value in the list.

Avoid duplicating the domain suffix when a form already appends it. A verification request for one subdomain is not necessarily a request for the root. Preserve the supplied content rather than adding extra labels or explanatory text inside it.

Complete and check verification

Return to the requesting service and run its verification check. If it fails, compare the hostname and value it is checking with the actual authoritative DNS answer. A successful save in the module proves a provider update, not that another service has refreshed its cached lookup.

Check the domain’s active nameservers and allow for DNS caching before repeatedly generating new verification values. Use the latest value requested by that service, especially after restarting a verification flow.

Keep other TXT records intact

A domain can have TXT records for several purposes. Do not replace SPF, DKIM or another service’s verification record merely because they share a type. If a value must be removed after verification, follow that service’s instructions; some services require it to remain for continued verification.

If an edit is blocked, your hosting team should check the zone assignment, locks, managed records and limits. Retain the record name and original redacted error without exposing unrelated account tokens or credentials.

Check the verification hostname and value

Your hosting team should compare the requesting service’s latest intended hostname and value with the saved full TXT name and actual authoritative answer. Check for a repeated domain suffix, stale verification flow, cached lookup, assignment, zone lock, managed record or allowance. Successful record publication does not mean another service has refreshed its lookup. Describe any value mismatch without attaching unrelated verification values or replacing another service’s TXT record.

See the PD Cloudflare DNS WHMCS guide for related tasks, or explore the module.