Hi Railway team,

Custom domain stuck in VALIDATING_OWNERSHIP for ~24h.

ACME TXT challenge is never published on Railway's authorize.railwaydns.net target.

Project: care

Project ID: fdaca019-61fe-48c0-a0e7-dea468db8a55

Service: care (070dd042-2e37-4536-9494-7eda021bec61)

Environment: production (6497d8f8-932f-4d0a-b369-8529b0b100e8)

Domains affected:

1. care.lnctec.com.br (id: f05af03a-526d-4d05-a0c0-4cfc66cc12a4)
   • CNAME care → xce08g5z.up.railway.app — PROPAGATED
2. *.care.lnctec.com.br (id: 5b672a47-0d97-4cf7-8476-c236e17d8948)
   • CNAME *.care → mr6sgu4i.up.railway.app — PROPAGATED
   • CNAME _acme-challenge.care → mr6sgu4i.authorize.railwaydns.net — PROPAGATED

Symptoms:

• Both domains stuck in VALIDATING_OWNERSHIP indefinitely

• dig TXT mr6sgu4i.authorize.railwaydns.net → returns empty

  (Railway is not publishing the ACME challenge token on its side)

• HTTPS requests to https://care.lnctec.com.br return 404 "train not arrived"

Already tried:

• Deleted and recreated both custom domains (twice)
• Verified DNS propagation globally via dig from multiple resolvers
• Confirmed Cloudflare proxy is DISABLED (DNS only / grey cloud) on all 3 CNAMEs
• Waited 24h+ between attempts

This looks like an issue on Railway's ACME provisioning side since the

authorize.railwaydns.net TXT record is never populated.

Could someone from the team trigger a manual re-validation or check why

the ACME challenge isn't being published for these domain IDs?

Thanks!