3 hours ago
Hi Railway team,
Our two custom domains have been stuck in VALIDATING_OWNERSHIP since we pointed the DNS this morning. The TXT ownership records are published and correct, but verification has not moved. This is our company's live website and the old host is no longer in DNS, so the site is down for all visitors right now.
Project: plastimex-cotizador, environment production, service plastimex-cotizador. Domain IDs: plastimex.mx = 0a8a8162-0396-4041-92dc-ef929e49c4cc, www.plastimex.mx = d3abf713-baab-46e8-bc97-72f3a3956808. Both were created on 2026-11-14 at 02:54 UTC; the DNS was changed on 2026-11-18, before 14:20 UTC.
DNS is on Cloudflare in DNS-only mode (grey cloud), with no CAA records and no DNSSEC. The same answers come back from 1.1.1.1, 8.8.8.8, 9.9.9.9 and the authoritative nameservers (rick/zara.ns.cloudflare.com): plastimex.mx is a CNAME to ikspc3tn.up.railway.app (flattened at the apex, resolves to 153.52.255.85); www.plastimex.mx is a CNAME to kptgomi1.up.railway.app; _railway-verify.plastimex.mx and _railway-verify.www.plastimex.mx are TXT records whose 64-character tokens exactly match what railway domain status shows.
What Railway reports: railway domain status shows the CNAME as DNS_RECORD_STATUS_PROPAGATED, but verified: false and CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP. The edge serves the *.up.railway.app certificate and returns 404 "Application not found" with x-railway-fallback: true. railway domain certificate retry answers that a retry is only available after issuance fails.
Could you re-run ownership verification and certificate issuance for these two domains? Thank you!
0 Replies
Status changed to Awaiting Railway Response Railway • about 2 hours ago