DNS propagation stuck: how to verify globally

Not specified by the original author.

TL;DR

DNS "propagation" is really just TTL expiry plus caching: check the authoritative nameserver first (that is the truth), then check public resolvers worldwide to see who has picked it up. If the authoritative server shows the new record, you are done and just waiting on TTL; if it shows the old one, the change never applied. Most "stuck propagation" is a change made at the wrong nameserver.

Error / query

DNS propagation stuck: how to verify globally

Use this skill when

• You changed a DNS record and some users still see the old value hours later
• You need to prove to someone that the change is live (or is not)
• A migration depends on the new record being visible everywhere
• You suspect the change was made at the wrong DNS provider

Not for this skill when

• Nothing resolves at all; that is an outage, not propagation
• The record is correct everywhere but the app misbehaves; the problem is not DNS
• You are waiting on domain registration or nameserver delegation changes; those take up to 48h regardless

Steps

Step 1: Ask the authoritative nameserver directly

dig +short example.com @ns1.exampledns.com

Expected: the new IP; the authoritative server is the source of truth, replace ns1.exampledns.com with your domain's real nameserver.

Step 2: Find which nameservers are actually authoritative

dig +short NS example.com

Expected: the NS list; if this does not match where you made the change, you edited the wrong provider and nothing will ever propagate.

Step 3: Check what public resolvers see

for r in 8.8.8.8 1.1.1.1 9.9.9.9; do echo -n "$r: "; dig +short example.com @$r | head -1; done

Expected: the new IP from all three; mixed old/new means TTL has not expired everywhere yet.

Step 4: Check the TTL on the record

dig +noall +answer example.com | head -2

Expected: the second field is the remaining TTL in seconds; that number is literally how long the wait is.

Step 5: Verify from multiple geographies

curl -s 'https://cloudflare-dns.com/dns-query?name=example.com&type=A' -H 'accept: application/dns-json' | head -c 400

Expected: JSON with the new IP; this queries from Cloudflare's edge, a different vantage point than your local resolver.

Variant phrasings

"How long does DNS propagation take"

As long as the old TTL; if the TTL was 3600, expect up to an hour. Lower the TTL to 300 a day before a planned change.

"DNS checker shows different results worldwide"

Normal during the TTL window; worry only if the authoritative server (step 1) shows the wrong value.

"Changed DNS but nothing happened"

You almost certainly edited records at a provider that is not authoritative; step 2 catches this in ten seconds.

Why it happens

Resolvers cache records for the TTL duration, so "propagation" is just caches expiring one by one. It feels stuck when the TTL was long, when someone cached the old value just before your change, or when the change went to the wrong nameserver entirely.

Edge cases and pitfalls

• Browsers and OSes cache DNS too; a correct dig plus a broken browser means clear the local cache, not the DNS.
• Negative caching: a failed lookup gets cached too, so a typo'd record poisons resolvers for the negative TTL.
• Some ISPs ignore TTLs and cache longer; you cannot fix that, only wait or ask users to switch resolvers.
• CNAME at the apex is invalid; if the root domain "propagates" everywhere except some resolvers, check for that.

Provenance

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

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

Thread query: DNS propagation stuck: how to verify globally

TL;DR: DNS "propagation" is really just TTL expiry plus caching: check the authoritative nameserver first (that is the truth), then check public resolvers worldwide to see who has picked it up. If the authoritative server shows the new record, you are done and just waiting on TTL; if it shows the old one, the change never applied. Most "stuck propagation" is a change made at the wrong nameserver.

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.