Hello Railway team,

Custom domain ownership verification is stuck even though both required DNS records are correct and publicly propagated.

Domain: geopodklady.adeon.cz

Project: AdeonMapDownloader

Project ID: a27e7c1f-4727-443b-a0fe-a342de2b7203

Environment: production

Environment ID: 661a367e-1a40-447e-bdec-67be24464567

Service: AdeonMapDownloader

Service ID: 3274adb3-c318-42cf-9469-25b03abfc7b2

Deployment ID: 5488cffe-adc7-4bbf-9c82-942652d1f97e

Target port: 8080

Plan: Hobby

Railway dashboard and CLI currently report:

• syncStatus: ACTIVE
• CNAME status: PROPAGATED
• verification.verified: false
• certificate status: VALIDATING_OWNERSHIP
• dashboard: Waiting for DNS update

Published DNS records:

• CNAME geopodklady.adeon.cz -> 9ynp2bb4.up.railway.app
• TXT _railway-verify.geopodklady.adeon.cz -> railway-verify=7f263782deed00852aa678522e61c6e0a991749632558e9330a45acfbcd6fc14

The records resolve from all authoritative Websupport nameservers, Google DNS, and Cloudflare DNS. DNSSEC validates successfully and there is no restrictive CAA record.

The custom hostname reaches Railway but returns the Railway fallback 404 with x-railway-fallback: true and serves the *.up.railway.app certificate. Example request ID at 2026-09-01 09:00 CEST: yufm7DYGRn2WAONS63j4Ww.

The Railway-provided hostname is healthy and /health returns HTTP 200. I also refreshed the custom domain with a no-op update to the existing target port 8080. The CLI certificate retry is unavailable because the status is still VALIDATING_OWNERSHIP rather than FAILED.

Could the Railway team please manually re-run ownership verification and trigger certificate re-issuance for this domain?

Thank you.