URGENT: Custom domain stuck in VALIDATING_OWNERSHIP despite correct DNS for 11+ hours
karima-skool
HOBBYOP

14 days ago

Domain: events.karima.org.uk (id e39a5995-b046-4b4f-a588-fd1af175c0b9), project karima-platform, service karima-web, production environment.

Timeline: the domain was added 3 Aug 21:35 UTC. The DNS records were created at the registrar's nameservers ~22:00 BST (21:00 UTC) on 6 Aug. Since then, your API reports the CNAME record as DNS_RECORD_STATUS_PROPAGATED — so your backend has successfully resolved our DNS - but verification.verified has remained false for 11+ hours.

DNS evidence: the TXT record at _railway-verify.events.karima.org.uk matches verification.token byte-for-byte. Confirmed resolving correctly from the authoritative nameservers (ns1/ns2.rochendns.com, both consistent) and from 1.1.1.1, 8.8.8.8 and 9.9.9.9 - three DNSSEC-validating public resolvers - which rules out signing or propagation problems. The CNAME (events → mtfulf4q.up.railway.app) resolves correctly from all of the same.

No self-service path exists for this state: railway domain certificate retry is refused because the status is VALIDATING_OWNERSHIP rather than FAILED.

Our read: the ownership-validation job likely exhausted its retry schedule during the 3–6 Aug window before the DNS records existed, and has not restarted now that DNS is correct - while the separate record-propagation checker clearly has run and updated.

Request: could you either force the ownership-validation job to re-run server-side, or manually mark ownership verified - ideally without issuing a new token? The evidence above shows the records have been correct and globally resolvable for 11+ hours.

This is blocking a Charity website launch. Happy to provide any further diagnostics.

Solved

3 Replies

Status changed to Awaiting Railway Response Railway 14 days ago


karima-skool
HOBBYOP

14 days ago

Hey, could I ask for an ETA or escalation? We're in the process of a migration, so the old site is down


karima-skool
HOBBYOP

14 days ago

Can someone from the infrastructure team respond with an ETA? We need resolution within the next few hours, it's been 15+ hours now since the DNS change took place


14 days ago

Your diagnosis is correct. The ownership-validation workflow exhausted its retries before the DNS records were in place and never re-ran once they propagated. We've re-triggered certificate issuance for events.karima.org.uk, which should complete within a few minutes.


Status changed to Awaiting User Response Railway 14 days ago


Status changed to Solved brody 14 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...