Hello Railway team, My domain is wafraan.com. Deployment is successful. I have verified: - CNAME points to the Railway hostname. - _railway-verify TXT record exists. - DNS propagation is complete on Google (8.8.8.8) and Cloudflare (1.1.1.1). - dig resolves correctly. - The Railway service is online. However Railway still shows: "Waiting for DNS update" and HTTPS serves a Railway certificate instead of issuing one for wafraan.com. Could you please check the custom domain verification and SSL provisioning on your side? Thank you.

Custom domain stuck on "Waiting for DNS update" although DNS propagation is complete

wafraan

FREEOP

15 days ago

Hello Railway team,

My domain is wafraan.com.

Deployment is successful.

I have verified:

CNAME points to the Railway hostname.
_railway-verify TXT record exists.
DNS propagation is complete on Google (8.8.8.8) and Cloudflare (1.1.1.1).
dig resolves correctly.
The Railway service is online.

However Railway still shows:

"Waiting for DNS update"

and HTTPS serves a Railway certificate instead of issuing one for wafraan.com.

Could you please check the custom domain verification and SSL provisioning on your side?

Thank you.

Solved

3 Replies

Railway

BOT

15 days ago

Your CNAME record for wafraan.com is pointing to w187zpzh.up.railway.app, but the current Railway target for this domain is xmo6xlox.up.railway.app. Update the CNAME at your registrar to point to xmo6xlox.up.railway.app, and once it propagates, verification and certificate issuance will proceed automatically.

Status changed to Awaiting User Response Railway • 15 days ago

wafraan

FREEOP

15 days ago

Thank you.

I have updated the CNAME as requested.

It now points to xmo6xlox.up.railway.app.

I have confirmed using both Google DNS (8.8.8.8) and Cloudflare DNS (1.1.1.1):

dig +short wafraan.com

xmo6xlox.up.railway.app.

69.46.46.104

dig @8.8.8.8 +short wafraan.com

xmo6xlox.up.railway.app.

69.46.46.104

DNS propagation is complete.

However the Railway dashboard still shows Waiting for DNS update, and HTTPS is still serving the Railway certificate instead of issuing one for wafraan.com.

Could you please refresh the domain verification or trigger SSL provisioning on your side?

Status changed to Awaiting Railway Response Railway • 15 days ago

Railway

BOT

15 days ago

Your CNAME is now correctly propagated, but the domain's ownership verification has not completed. Please confirm your TXT record is set on the _railway-verify.wafraan.com hostname (not the root domain) and that its value exactly matches the verification token shown on your domain's settings page in the Railway dashboard. If the record name or value differs even slightly, verification will not pass and the certificate will not issue.

Status changed to Awaiting User Response Railway • 15 days ago

Railway

BOT

8 days 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 • 8 days ago

Welcome!