Custom domain stuck on "Waiting for DNS update" with cert not issued, despite everything verifying correctly
emilek33
HOBBYOP

a month ago

Project: zonal-dream / Service: hyperspeed-web / Env: production

Custom domain: www.hyperspeedteam.com

Railway-issued CNAME target: mxkmrq1t.up.railway.app

Port: 3000 (matches the working hyperspeed-web-production.up.railway.app URL on the same service)

DNS verified: nslookup -type=CNAME www.hyperspeedteam.com against both 1.1.1.1 and 8.8.8.8 returns mxkmrq1t.up.railway.app; globally green on dnschecker.org

Service is Online, latest deployment is healthy, hyperspeed-web-production.up.railway.app works fine

Hitting https://www.hyperspeedteam.com returns Railway's edge 404 "The train has not arrived at the station" page (Request ID: kiontIXqQles8BiCnpoFkQ) — so traffic is reaching Railway's edge but the domain isn't bound to the service

Already tried: remove + re-add the custom domain (twice), hard-refresh dashboard, updated GoDaddy CNAME each time Railway assigned a new target

Status page is green, no known incident

Please kick the verifier / force the binding.

Solved$10 Bounty

Pinned Solution

You need to add a TXT record to _railway-verify.www.hyperspeedteam.com. If you are using the API to add your custom domain you can find the TXT record in verificationToken under status

1 Replies

Status changed to Open Railway about 1 month ago


You need to add a TXT record to _railway-verify.www.hyperspeedteam.com. If you are using the API to add your custom domain you can find the TXT record in verificationToken under status


Status changed to Awaiting User Response Railway about 1 month ago


Status changed to Solved 0x5b62656e5d 22 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...