Delay in Custom Domain Propagation on Railway
cleaningbizai
PROOP

a year ago

I'm experiencing a delay in custom domain propagation on Railway, even though the changes have already been propagated from Cloudflare.

small_blue_diamond emojiWhat I did:
white_check_mark emoji Updated DNS records on Cloudflare (A/CNAME pointing correctly).
white_check_mark emoji Confirmed propagation via DNS lookup tools (records are updated).
white_check_mark emoji Flushed DNS cache on my local machine.

small_blue_diamond emojiIssue:

  • Despite these updates, my custom domain isn’t resolving to my Railway-deployed site.

  • I’ve waited for a while, but the domain still redirects incorrectly or fails to load.

  • Railway panel still shows “Pending” for domain verification.

small_blue_diamond emojiQuestions:
one emoji Is there an additional Railway-side caching delay?
two emoji Should I manually re-trigger verification or re-add the domain?
three emoji Any troubleshooting steps specific to Railway + Cloudflare setup?

Would appreciate any insights! Thanks in advance. rocket emoji

Solved

1 Replies

itsrems
EMPLOYEE

a year ago

Heya, can you send a screenshot of your cname record in cloudflare ?

Status changed to Awaiting User Response Railway • 12 months ago

Railway
BOT

7 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 7 months ago

Loading...