Custom domains stuck on “Waiting for DNS update” – certificate re-issuance needed
idunnpeptide-lab
HOBBYOP

13 days ago

Domains:

replyhalo.com

www.replyhalo.com

Both custom domains have been stuck on “Waiting for DNS update” for more than 8 hours.

The required DNS routing and TXT verification records are configured, but Railway is still not verifying the domains.

The application is healthy and deployed successfully.

Please help verify the DNS records and re-trigger domain verification/certificate issuance if necessary, without deleting or recreating the custom domains.

Thank you.

Solved

1 Replies

Railway
BOT

13 days ago

Neither domain is verified yet because we can't find either TXT verification record on the public internet, so both certificates are held at the ownership check and a re-issue would stop at the same point. For the root domain, add a TXT record with host _railway-verify and value railway-verify=cd52207c5c5e4ac656b806fbeb9e570fec9c9507060f2db741674b859e6c303a. For the www subdomain, add a TXT record with host _railway-verify.www and value railway-verify=fca10b556e2317f670b542312675380fe857218e4ec83f2b08334adef0dc536e. Enter each value exactly as shown, and enter the host exactly as shown too, since your DNS provider adds the domain on its own. Verification and certificate issuance continue automatically once the records propagate, so you don't need to remove and re-add the domains.


Status changed to Awaiting User Response Railway • 13 days ago


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...