domain verification cname record not found pending

domain verification cname record not found pending

TL;DR

The verifier queries public DNS and finds nothing, so check what is actually published with dig. Compare the hostname and value against exactly what the provider asked for, fix typos and doubled domains, wait out the TTL across multiple resolvers, then click verify again.

domain verification cname record not found pending

Use this when

• Domain verification sits at pending for hours or days
• The provider reports the CNAME record was not found
• Verification worked for other domains but not this one

Not for this skill when

• TXT record verification failing (different record type)
• The record exists but the value mismatches (content problem)
• Verification failing instantly rather than pending (check the provider status)

Steps

Step 1: Query the record directly

Run dig for the exact hostname the provider expects and inspect the answer section. Expected: you see what public DNS actually returns, which may be nothing.

Step 2: Compare against the requirement

Put the provider's required host and value next to the dig output, watching for trailing dots and doubled domains. Expected: you spot the discrepancy, often a typo or wrong host.

Step 3: Fix the DNS record

Correct the CNAME host and value at your DNS provider. Expected: the record matches the requirement exactly.

Step 4: Wait for propagation

Wait out the record's TTL and re-check with several public resolvers. Expected: multiple resolvers return the correct record.

Step 5: Re-run verification

Click verify in the provider dashboard. Expected: the status flips from pending to verified.

Tool compatibility

DNS management (any provider); dig and public resolvers; domain verification flows (SaaS providers generally).

Variant phrasings

Variant 1

domain verification cname not found how long

Variant 2

cname verification stuck pending dns

Variant 3

domain ownership verification cname record missing

Why it happens

Domain verification is the provider asking public DNS a question and waiting for the right answer; pending means the answer never came. The record is usually wrong rather than merely slow: DNS editors that auto-append the domain turn host entries into doubled names, CNAMEs get placed at the apex where they are illegal, or the value was copied with a typo. Propagation delay is real but measured in TTLs, not days, so a verification pending for 72 hours is a wrong record, not a slow internet. Checking with dig against multiple resolvers separates the two cases in seconds.

Edge cases / pitfalls

• Some DNS UIs append the domain to the host field automatically; entering the full hostname doubles it.
• CNAME cannot coexist with other records at the same name, including at the apex; use ALIAS or ANAME there.
• Negative caching means a wrong lookup can persist for the TTL even after you fix the record; wait it out.

Provenance

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