domain verification txt record missing not working

Fix domain verification failing on a missing TXT record

TL;DR

Verification fails when the TXT record is missing, misnamed, or not yet visible. Add the exact TXT record the provider gave you at the exact host they named, then check it with dig before clicking verify. Most failures are a wrong host field, not propagation.

The error

Domain verification failed
TXT record not found. Verification could not be completed.

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=domain verification txt record missing not working"

Fix it

Step 1: Copy the exact record from the provider

In the provider's verification screen, copy the host and value character by character.

Expected: You have the exact strings, no retyping.

Step 2: Add the TXT record in your DNS

Create the TXT record with the given host and value in your DNS provider.

Expected: The record exists in your zone.

Step 3: Check it with dig before clicking verify

dig TXT [host].[domain] and confirm the value appears.

Expected: The record is publicly visible. If not, fix the host field first.

Step 4: Click verify

Return to the provider and run verification.

Expected: Verification succeeds.

Step 5: Leave the record in place if required

Some providers re-check periodically; check whether removal is safe.

Expected: The record stays or is removed per the provider's guidance.

When this applies

• Domain verification fails on a missing TXT record
• You just added the record and it still fails
• You are verifying a domain for a new service

When it doesn't

• The record exists and dig sees it but verification fails (check the value for typos)
• You need CNAME or MX verification (different record type)
• The domain is not delegated to your DNS provider (fix delegation first)

Compatibility

DNS TXT verification generally: Google, Microsoft, SaaS domain verification.

Variant phrasings

txt record missing domain verification

Same failure. The host field is the usual culprit; providers differ on whether to include the domain.

domain verification txt not found

Not found with a correct record usually means the host was entered with the domain appended twice.

verify domain txt record not propagating

True propagation delay is rare for new records. A wrong host is far more common than slow DNS.

Why it happens

Verification is a simple lookup: the provider queries the exact host for the exact value. DNS management UIs differ on whether the host field wants the bare subdomain or the full name, so people create the record at the wrong name and the lookup finds nothing. Propagation is blamed far more often than it is guilty.

Edge cases

• Some DNS providers append the domain automatically; entering the full name double-appends it
• TXT values with quotes or spaces must be entered exactly; extra quoting breaks the match
• CNAME at the same host shadows the TXT record; remove conflicts

If it still fails

• Verify from multiple networks; one network's cache is not the internet's state.
• Check the domain's delegation and nameservers before blaming individual records.
• Wait out one full TTL after a fix before declaring it still broken.
• Keep a known-good dig output to diff against during the next incident.
• If a provider's verification never passes with correct records, escalate with dig output and timestamps.

Prevention

• Lower TTLs a day before any planned DNS change.
• Verify every record with dig against authoritative before declaring done.
• Monitor certificate and domain expiry with alerts, not memory.
• Keep DNS change history; most outages are a bad edit, not propagation.
• Test verification flows in staging with a throwaway subdomain.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_jBAizMMPjpWJhimX8uCXEA