Hello Railway Support,

Our production custom domain has remained unverified and unrouted for more than 72 hours.

Railway project: onward-prod

Project ID: 15630dbc-31fe-436f-b8c7-592a8e011196

Environment: production

Service: onward-prod

Custom domain: onwards.work

Railway domain ID: 281fa808-0288-4376-98f6-8da7e2a88eee

Created: 2026-09-04T11:35:49Z

Current Railway status:

• syncStatus: ACTIVE
• DNS record status: DNS_RECORD_STATUS_PROPAGATED
• required CNAME: g08ul9qc.up.railway.app
• verification.verified: false
• certificate status: CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP
• CDN provider: Cloudflare

DNS was rechecked against Railway’s documented Cloudflare setup:

• Cloudflare authoritative nameservers:

  jake.ns.cloudflare.com

  kami.ns.cloudflare.com

• Apex CNAME in Cloudflare:

  onwards.work -> g08ul9qc.up.railway.app

• Apex proxy: enabled

• www CNAME:

  www.onwards.work -> onwards.work

• Railway verification TXT exactly matches the current token shown by Railway.

• The TXT value matches at the authoritative nameserver and at 1.1.1.1, 8.8.8.8, and 9.9.9.9.

• No CAA records are present.

• DNSSEC is disabled.

• Cloudflare SSL mode is Full, not Full Strict.

• Universal SSL is enabled.

• The Cloudflare proxy was temporarily disabled and restored as recommended.

Could you please inspect the ownership-verification and certificate-issuance state for this domain and confirm:

1. Whether Railway’s verifier sees the expected CNAME and TXT records.
2. Why DNS is reported as propagated while ownership remains unverified.
3. Whether the custom-domain verification/certificate state can be safely refreshed or retriggered.

We have not deleted and recreated the domain, to avoid Let’s Encrypt duplicate-certificate rate limits.

Thanks a lot!!!