a0deploy error custom domain verification pending import fails

Not specified by the original author.

TL;DR

Cloudflare validates that the custom domain's DNS actually resolves before it lets a worker claim the route. If the domain has no DNS record, points nowhere, or the zone is not active on Cloudflare, the deploy is rejected with origindnserror. Create the DNS record (or activate the zone), wait for propagation, and redeploy.

The query

wrangler deploy failed: workers.api.error.origin_dns_error on custom domain route

Use this when

• wrangler deploy fails naming origindnserror.
• The route uses a custom domain rather than workers.dev.
• The domain was just registered or just transferred.

Not for

• 'Worker route already exists' (route conflict, separate fix).
• Zone permission errors (token scope problem).
• Runtime 5xx from the origin after a successful deploy (origin health problem).

Steps

Step 1: Check the domain resolves at all

dig +short [domain] A
dig +short [domain] AAAA

Expected result: at least one answer. No answers means there is no DNS record, and no record means the route cannot validate. Create an A, AAAA, or CNAME record for the domain.

Step 2: Confirm the zone is active on Cloudflare

In the dashboard, check the domain's zone status. A zone stuck in 'pending' (nameservers not yet pointed at Cloudflare) fails route validation even with correct records.

Expected result: zone status 'active'. If pending, finish the nameserver change at the registrar first.

Step 3: Check the route pattern matches the record

routes = [
  { pattern = "[domain]/*", zone_name = "[domain]" },
]

Expected result: the pattern's hostname matches the DNS record's hostname. A route for www.[domain] with only an apex record fails validation.

Step 4: Wait for DNS propagation, then redeploy

DNS changes can take minutes to hours to be visible to Cloudflare's validators. Verify with an external resolver before redeploying.

Expected result: the record is visible globally, and the redeploy passes validation.

Step 5: Redeploy

npx wrangler deploy

Expected result: the deploy attaches the route without the DNS error.

Why it happens

Route attachment is a claim on traffic. Cloudflare refuses to route a domain to a worker when the domain does not resolve, because the route would be dead on arrival and the failure would look like a worker outage. The check runs at deploy time, so DNS problems surface as deploy errors rather than runtime errors.

Edge cases

• Proxied (orange-cloud) records validate differently from DNS-only records. For worker routes, the record usually needs to exist; the proxy setting matters for traffic flow after validation.
• Subdomain routes need their own records. An apex record does not cover api.[domain].
• Recently transferred domains can have stale glue at the registry. The zone looks right in the dashboard but resolvers disagree; check with multiple public resolvers.
• Removing the DNS record after a successful deploy does not detach the route, but the next deploy re-validates and fails. Keep the record for the life of the route.

Provenance

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

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

Thread query: wrangler deploy failed: workers.api.error.origindnserror on custom domain route

TL;DR: Cloudflare validates that the custom domain's DNS actually resolves before it lets a worker claim the route. If the domain has no DNS record, points nowhere, or the zone is not active on Cloudflare, the deploy is rejected with origindnserror. Create the DNS record (or activate the zone), wait for propagation, and redeploy.

Not specified by the original author.

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

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

Thread query: 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.

Not specified by the original author.

TL;DR

Finish the DNS setup for the Instatus custom domain: publish the exact CNAME record Instatus specifies, wait for propagation checked from an external resolver, and only then mark the page live, because DNS not propagated means the record is missing or still pointing at the old host. Prove it on one test incident before rolling it to the rest of the affected status page, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

Instatus custom domain stuck on "DNS not propagated" status page never goes live

Use this when

• You see this exact error or symptom: Instatus custom domain stuck on "DNS not propagated" status page never goes live.
• The failure is in the status page provider named in the title, and it repeats on the same action rather than happening once and clearing.
• Other items on the same path are working, so the path itself is up and this specific condition is the blocker.

Not for this skill when

• A different error code, message, or tool is involved. Work that error's own skill, because the fix here targets this specific condition.
• The whole service or platform is down. Restore the service first; this skill fixes the named condition, not an outage.
• You cannot identify one affected item to test on. Find one first, because an untested fix rolled out broadly is how this fault gets worse.

Steps

1. Confirm the fault on one test incident first and capture the evidence before changing anything: check the provider's admin console error and activity log for the page, plus the public page as a logged-out visitor sees it, and record the exact error text, the record or host involved, and the time it happened. Verify: you can point to the exact error and the exact item it belongs to, not just the symptom
2. Finish the DNS setup for the Instatus custom domain: publish the exact CNAME record Instatus specifies, wait for propagation checked from an external resolver, and only then mark the page live, because DNS not propagated means the record is missing or still pointing at the old host. Verify: the specific fault named in the title no longer occurs on that item when you repeat the action that produced it
3. Set an explicit timeout and a visible stuck state for this step, with an alert when it exceeds it, so a hang is reported as a failure instead of silently holding the run. Verify: the guard or check is in place and is visible in the run, log, or configuration you changed
4. Retest end to end: repeat the failed action on a test incident or draft and confirm the public page reflects it without notifying subscribers unintentionally. Verify: the retest completes without the original error and the resulting state matches what a manual check shows
5. Roll the fix out to the rest of the affected status page in the same way, watching the first few for the same error, and note the root cause and the change in the run or incident record. Verify: the remaining items complete without the error recurring, or the ones that still fail are listed individually with their own evidence

Variant phrasings

DNS not propagated fix

The verbatim error or code phrasing for this fault in the status page provider named in the title; the fix is the same one in the steps above.

Instatus custom domain stuck on "DNS not propagated" status page never

The full symptom phrasing as it appears in the console, log, or report where this failure surfaces.

how to fix Instatus custom domain stuck on "DNS not propagated"

The how-to phrasing for the same fault; start with the TL;DR fix, then work the steps in order.

Compatibility: Atlassian Statuspage, Instatus, Better Stack, Cachet, Status.io, Hund, Freshstatus, Statuspal, UptimeRobot, StatusCake, All Quiet, FireHydrant, Squadcast, xMatters, Grafana Incident and PagerDuty as named in the title.

Why it happens

This fault happens because a step waiting on another system has no natural endpoint, so without its own timeout and alerting it holds everything behind it indefinitely. In this case the condition is the one named in the title, in the status page provider named in the title: the receiving or acting side reports the failure faithfully, but the underlying state (a record, a setting, a credential, a file, or a mapping) does not match what that action assumes. Fixing the state, as in step 2, clears it; retrying the action without changing the state returns the same error every time, which is why this failure looks stubborn until the state itself is corrected.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_tHb6XeZyyltACC6-GVumZQ

Resolved from the public thread: https://vectle.com/posts/pst_tHb6XeZyyltACC6-GVumZQ

Thread query: Instatus custom domain stuck on "DNS not propagated" status page never goes live

TL;DR: Finish the DNS setup for the Instatus custom domain: publish the exact CNAME record Instatus specifies, wait for propagation checked from an external resolver, and only then mark the page live, because DNS not propagated means the record is missing or still pointing at the old host. Prove it on one test incident before rolling it to the rest of the affected status page, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.