agent failed with timeout waiting for dns propagation on dns-01

Not specified by the original author.

Fix DNS propagation stuck during new domain onboarding

TL;DR

Propagation that seems stuck is usually a wrong record or a cached old value, not slow DNS. Check the record with dig against the authoritative nameserver first; if it is wrong there, fix it. Only then blame caching, and lower the TTL for the next change.

The error

DNS propagation stuck
New domain records not visible after many hours. Onboarding blocked.

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=dns propagation stuck new domain onboarding"

Fix it

Step 1: Query the authoritative nameserver directly

dig @[nameserver] [record] [type] for the record in question.

Expected: If the authoritative server shows the wrong value, the record itself is wrong. Fix it there.

Step 2: Check public resolvers

Query a couple of public resolvers and compare.

Expected: If they differ from authoritative, you are seeing cache; note the remaining TTL.

Step 3: Fix the record if wrong

Correct the value at your DNS provider.

Expected: Authoritative answers are now correct.

Step 4: Wait out the TTL or flush where you can

Wait for the old TTL to expire; flush local and OS caches in the meantime.

Expected: Resolvers converge on the new value as TTLs expire.

Step 5: Lower TTLs before the next change

Drop the TTL to a few minutes well ahead of future changes.

Expected: The next change propagates in minutes, not hours.

When this applies

• New domain DNS changes seem stuck for hours
• Onboarding is blocked waiting on DNS
• You are cutting a domain over to new infrastructure

When it doesn't

• The authoritative server is correct and resolvers agree (the problem is elsewhere)
• The domain does not resolve at all (check delegation and nameservers)
• Only one network sees the old value (that network caches aggressively)

Compatibility

DNS generally. dig and standard resolver behavior.

Variant phrasings

dns not propagating new domain

Same troubleshooting. Authoritative first, then caches.

dns changes taking too long

Too long usually means a high TTL was set before the change. Lower TTLs ahead of changes.

domain onboarding dns stuck

Onboarding checklists that wait on DNS should verify against authoritative servers, not public ones.

Why it happens

DNS has two layers: what you published (authoritative) and what resolvers remember (cache). Most stuck propagation is actually a wrong authoritative record, and the rest is resolvers honoring a long TTL you set before the change. True propagation delay beyond TTL expiry is rare.

Edge cases

• Some ISP resolvers ignore TTLs and cache longer; you cannot fix their behavior
• Negative caching means a queried-missing record stays missing for the negative TTL
• Changing nameservers themselves takes the longest; plan those moves carefully

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_nh1Qf48eqrN3u998rwAbZw

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

Thread query: dns propagation stuck new domain onboarding

TL;DR: Propagation that seems stuck is usually a wrong record or a cached old value, not slow DNS. Check the record with dig against the authoritative nameserver first; if it is wrong there, fix it. Only then blame caching, and lower the TTL for the next change.

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.

Not specified by the original author.

Unstick the agent waiting on a DNS TXT record it misconfigured

TL;DR

The agent wrote the wrong TXT value or the wrong host, so verification will never pass no matter how long it waits. Verify the record independently with a DNS lookup, delete the wrong record, write the exact host and value the provider shows, then re-check.

The problem

provider asks for: host "_verify", value "abc123xyz"
agent created: host "verify", value "abc123" (truncated)
agent status: waiting for DNS propagation... (6 hours and counting)

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=agent stuck waiting dns txt record it misconfigured"

Fix it

Step 1: Look up what actually exists in DNS

Query the record yourself with a DNS tool, for both the host the agent claims it created and the host the provider asked for.

Expected: you see the real TXT value in DNS, and you can compare it character by character with the provider's expected value.

Step 2: Delete the wrong record

Remove the misconfigured record from the DNS zone before writing the correct one. Leaving both creates ambiguity about which one the verifier reads.

Expected: a fresh lookup returns no TXT record at the wrong host.

Step 3: Write the exact host and value from the provider console

Copy the host and value directly from the provider's verification page - do not let the agent retype, truncate, or "clean up" the value. Quoted strings stay quoted exactly as shown.

Expected: the new lookup returns the exact value the provider expects.

Step 4: Wait for TTL, then trigger verification

Wait out the record's TTL, confirm the lookup is stable from two different resolvers, then click verify in the provider console.

Expected: verification passes on the first attempt after the correct record propagates.

Step 5: Put a verification gate in the agent's flow

After the agent writes any DNS record, the next step must be an independent lookup that compares the live value to the expected value, and the run must stop if they differ.

Expected: a misconfigured record fails fast with a diff instead of stalling for hours.

When this applies

• Domain verification stalls for hours with a TXT record the agent created
• The record in DNS does not match the provider's expected host or value
• The agent keeps polling instead of checking its own work

When it doesn't

• The record is correct and just propagating (check TTL and be patient)
• The provider's verification endpoint is down (verify from their status page)
• The failure is an SSL or CAA issue rather than TXT verification

Compatibility

SendGrid, Google Workspace, Microsoft 365, and any SaaS domain verification flow; Cloudflare, Route53, and other DNS providers for the record side.

Variant phrasings

domain verification stuck after agent added txt record

Same fix. "Stuck" almost always means "wrong" when an agent wrote the record.

agent keeps waiting for dns propagation that never completes

Propagation of a wrong value completes just fine - the verifier still rejects it. Compare values, not clocks.

Why it happens

Agents copy verification values through several steps - reading the console, storing in memory, writing to the DNS API - and each hop can truncate, reformat, or drop characters. Underscore-prefixed hosts get "normalized" away, long values get cut. The agent then polls for propagation of a record that is already fully propagated and simply wrong, and the loop has no step that compares the live value to the expected one.

Edge cases

• Multiple TXT records at the same host: some providers read only the first; delete extras
• DNS provider API caching: the write may succeed but read back stale for a minute
• Apex vs subdomain: the agent may have written the record at the wrong level of the zone

If it still fails

• Capture the expected host and value, the live lookup output, and the provider's exact error before changing anything else.
• Reproduce with a single test record so you are not debugging a crowd.
• Check the DNS provider and SaaS status pages; outages look exactly like config errors.

Prevention

• Agents never write DNS records without an immediate independent read-back and diff.
• Store verification values verbatim; never let the agent retype them.
• Cap DNS wait loops with a hard timeout and a value-diff check before giving up.

Provenance

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

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

Thread query: agent stuck waiting dns txt record it misconfigured

TL;DR: The agent wrote the wrong TXT value or the wrong host, so verification will never pass no matter how long it waits. Verify the record independently with a DNS lookup, delete the wrong record, write the exact host and value the provider shows, then re-check.