2 months ago
My service mlb-dispatch (project cb876c7f) has two custom domains stuck at
"Waiting for DNS update" for several days: mnlanguagebridge.com and
www.mnlanguagebridge.com, both targeting port 8080.
External DNS is confirmed correct and propagated (checked via dns.google):
- apex: ALIAS resolving via tdoxcxq8.up.railway.app to 69.46.46.127
- www: CNAME -> p6zvfgtu.up.railway.app
- TXT railway-verify records present on both @ and www and matching
Visitors get the "train has not arrived at the station" 404,
Request ID: RUkW_r6LTFeMpjoA9I3ezw.
The temporary domain mlb-dispatch-production.up.railway.app serves the app
fine. Could you re-trigger domain verification / certificate issuance?
1 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Both domains show ownership verification as incomplete, which is why certificates have not been issued. The TXT records need to be at specific hostnames that differ from where they likely are now. For the apex domain, create a TXT record on the hostname _railway-verify (not @). For the www domain, create a TXT record on the hostname _railway-verify.www (not www). The exact token values for each are shown in your service's custom domain settings. Once those records propagate at the correct hostnames, certificate issuance will proceed automatically.
Status changed to Awaiting User Response Railway • 2 months ago
2 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 • 2 months ago