Custom domain stuck on "Waiting for DNS update" for 8+ hours despite correct DNS
aicareerversestartup-glitch
HOBBYOP

7 days ago

Custom domains aicareerverse.com and www.aicareerverse.com stuck on "Waiting for DNS update" for 8+ hours. CNAME and TXT records are correctly set and confirmed globally propagated via DNSChecker.org (screenshot attached). Cloudflare proxy is DNS-only. Already tried deleting and re-adding the domain twice, and purged Cloudflare cache. Project: fantastic-miracle, Service: insightful-amazement (frontend). Please check server-side and manually re-trigger verification/certificate provisioning.'

Screenshot 2026-08-14 162010.png

Screenshot 2026-08-14 162050.png

Awaiting User Response

1 Replies

Railway
BOT

7 days ago

Both TXT verification records in your Cloudflare DNS are truncated, which is why verification is stuck. The values currently published at _railway-verify.aicareerverse.com and _railway-verify.www.aicareerverse.com are each missing their last 5 characters compared to what Railway expects. Copy the full verification values from the custom domain settings in your Railway dashboard (each domain shows the exact TXT value it requires) and re-enter them in Cloudflare, making sure the entire string is captured. Your CNAME records are both correct and propagated, so once the TXT values are fixed, verification and certificate issuance should proceed. Reply here once updated so we can confirm.


Status changed to Awaiting User Response Railway 7 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...