DNS text records
TXT records publish text through DNS. They are commonly used for SPF, DKIM, DMARC and service verification. Copy the host and value exactly from the provider requesting the record.
Host identifies the nameUse @ for the root domain or the exact selector/subdomain supplied.
Value is the published textCopy punctuation, spaces and provider tokens precisely.
Verify after savingQuery the authoritative DNS and allow for the previous TTL to expire.
What TXT records do
SPFLists services authorised to send mail for the domain.
DKIMPublishes a public key under a selector such as selector._domainkey.
DMARCPublishes policy and reporting instructions at _dmarc.
Service verificationProves domain control to Google, Microsoft and other platforms.
Understand the fields
@ for the root domain, or enter only the requested label such as _dmarc or google._domainkey. The panel normally appends the domain automatically.If a provider shows a fully qualified hostname ending with your domain, check whether the panel expects only the label. Entering the complete name into a panel that appends the domain can create name.example.com.example.com.
UKC DNS Manager
Open My DomainsSelect the domain, then open DNS Manager.
Check for an existing matching recordEdit it when replacing a policy; do not create conflicting duplicates.
Add TXTEnter the host and exact value supplied by the service.
Preview and saveReview the complete change before applying it.
Refresh and verifyConfirm the new value appears in the zone and then query public DNS.
Email safety
If SPF already exists, merge the required sender into that policy. Adding a second v=spf1 record can produce a permanent SPF error and harm delivery.
DKIM selectors can coexist because each uses a different host. DMARC should normally have one record at _dmarc. Preserve unrelated verification TXT records.
Verification
Use a DNS lookup for TXT records against the full name, for example the root domain, _dmarc.example.com or selector._domainkey.example.com. Confirm the returned text matches the provider’s value.
DNS caches can retain the previous answer until its TTL expires. A provider may also take additional time to repeat its verification check.
Need help?
Include the domain, active nameservers, required host, record type, complete value, provider/service name, and any verification error. For an email policy, include the existing related TXT records so they can be merged safely.
Record not verifying?Open a support ticket with those details. Never send an API key, service password or private DKIM key.
