Hi Railway team,

I have a custom domain whose certificate has been stuck at VALIDATING_OWNERSHIP for an extended period, despite DNS being fully correct and verified on your own end. I've deleted and recreated the domain more than once with identical results each time, so I don't think this is a DNS problem — requesting a manual look at whatever's blocking certificate issuance specifically.

Project: NovaStacs (5ddf038e-eeb7-45af-be38-bc038fb2c456)

Service: Digi_Agent (54c1cadd-7400-420d-b89a-48ae90b07643)

Environment: production (a71cd918-8f13-441c-bd93-f6bf6ca13e5c)

Domain: novastacs.com

Domain ID: edb99dbf-3b39-4b58-a487-3f30ae8fc9a5

What's confirmed correct on my end:

Domain sync status: ACTIVE

Ownership verification: verified: true

TXT record at _railway-verify.novastacs.com matches your required token exactly (independently reconfirmed via a live DNS lookup just now)

CNAME @ → p4sr08mg.up.railway.app, status PROPAGATED, matches required value exactly

No CAA record is restricting issuance (checked directly)

What's actually broken: certificate status has never progressed past VALIDATING_OWNERSHIP. A live HTTPS request to novastacs.com:443 doesn't even complete a TLS handshake — it times out with no response at all, which looks like a routing-layer issue rather than a certificate-validation one. For contrast, my Railway-provided domain (digiagent-production-c794.up.railway.app) serves correctly right now.

Could someone take a look at whether the cert-issuance process for this domain ID is stuck, or whether there's a leftover artifact from the earlier delete/recreate attempts blocking a fresh issuance?

Thanks,

railway domain status novastacs.com --json