Root domain stuck on "Waiting for DNS update" for 24+ hrs — DNS confirmed correct (Cloudflare)
rcolodzin
HOBBYOP

a month ago

Hi team, hoping someone can help take a look at the backend verification status for my domain.

Domain: susanerony.com

Situation: Custom domain has been stuck on "Waiting for DNS update" in the Railway dashboard for over 24 hours. DNS provider is Cloudflare (recently migrated from GoDaddy specifically to support this setup).

What I've confirmed on the DNS side:

CNAME: susanerony.com → kb60jzi4.up.railway.app, matching exactly what Railway's "Show DNS records" panel specified

TXT: _railway-verify record is present with the correct value Railway provided, set to "DNS only" (not proxied)

Both records confirmed fully propagated globally via whatsmydns.net

Cloudflare zone status shows Active, all 7 DNS records show clean status, nothing pending or in conflict

Also checked:

Ruled out CNAME flattening as the cause — confirmed Railway supports Cloudflare's flattened root records

Ruled out propagation delay — well past the typical window and confirmed via independent DNS checker

Since everything checks out cleanly on the DNS side and it's been well over 24 hours, I suspect this needs someone to check the domain's verification status directly on Railway's backend. Happy to provide screenshots or any other detail needed. Thanks!

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • about 1 month ago


a month ago

Your DNS is configured correctly and fully propagated, but the domain verification workflow stalled before it could pick up the records you added. We've started a certificate re-issue for the domain, which should complete the verification and get things working within a few minutes.


Status changed to Awaiting User Response brody • about 1 month ago


rcolodzin
HOBBYOP

a month ago

UPDATE: I deleted and recreated the www.susanerony.com custom domain, and updated DNS. All is working now, this is complete.

Thanks for this quick action. Going to https://susanerony.com now resolves to the site correctly, and has a cert.

I should have explicitly mentioned, this also applies to *.susanerony.com. Going to www.susanerony.com still does not resolve to the website, and is listed as waiting on DNS update. Can that one be nudged as well?

image.png

Attachments


Status changed to Awaiting Railway Response Railway • about 1 month ago


Status changed to Solved rcolodzin • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...