Custom domain stuck in VALIDATING_OWNERSHIP despite propagated DNS (apex, Cloudflare DNS-only)
dot3x3q
HOBBYOP

4 days ago

Apex custom domain deploy.social has been stuck in VALIDATING_OWNERSHIP for over an hour. DNS is on Cloudflare, record is DNS-only (grey cloud), and the flattened apex resolves correctly to the assigned target — your own dnsRecords status shows PROPAGATED. No CAA records, DNSSEC disabled. I've already deleted and recreated the domain once (the first attempt was briefly behind the Cloudflare proxy, which I suspect poisoned a cached validation state; the recreated domain has been DNS-only from the start and still won't validate).

Project: b54b048a-a2b4-4998-a014-969931d28e21 · Service: e228c09e-96c3-4c20-82c1-03c389facdb6 · Custom domain: deploy.social (id c4ee3382-d460-4d6e-90e7-1783e87c86c1). Could you flush the validation cache / re-trigger issuance?

Solved$10 Bounty

Pinned Solution

You need to add a TXT record for _railway-verify.deploy.social. If you are using the API to add your custom domain, you can find it in verificationToken under status.

2 Replies

Railway
BOT

4 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 4 days ago


You need to add a TXT record for _railway-verify.deploy.social. If you are using the API to add your custom domain, you can find it in verificationToken under status.


dot3x3q
HOBBYOP

4 days ago

Ah, totally missed this - you nailed it. Thank you for your quick reply!


Status changed to Solved 0x5b62656e5d 3 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...