Custom domain verification appears stuck
maxi-tb22
PROOP

a month ago

Custom domain verification appears stuck for service web-production-9b1f2. Domains www.the-test-of-time.com (CNAME → cbhv6gtv.up.railway.app) and the-test-of-time.com (ALIAS, resolves to your edge) have been verified correct on Google/Cloudflare/Quad9/OpenDNS public DNS, but the dashboard still shows "Waiting for DNS update" and the edge serves the *.up.railway.app wildcard cert. The domain recently transferred registrars (old nameservers ns1-3.wordpress.com are still answering with stale records) — suspect your resolver has the old delegation cached. Could you force a fresh verification?

Solved$20 Bounty

Pinned Solution

You need to add a TXT record to w_railway-verify.ww.the-test-of-time.com and _railway-verify.the-test-of-time.com. If you're using ther API, you can get the content from the verificationToken property under status.

2 Replies

Railway
BOT

a month ago

This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.

Status changed to Open Railway about 1 month ago


You need to add a TXT record to w_railway-verify.ww.the-test-of-time.com and _railway-verify.the-test-of-time.com. If you're using ther API, you can get the content from the verificationToken property under status.


maxi-tb22
PROOP

a month ago

Thank you so much! That did it!


Status changed to Solved 0x5b62656e5d about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...