Two custom domains on our production service have been stuck on "Waiting for DNS update" for over a week, and the ownership check appears to have stopped re-running (last check shown around Oct 23, possibly related to the Oct 21 incident).

Service: moveempire-app (production environment)

Domains: moveempire.app and www.moveempire.app, both on port 8080

DNS at Hostinger (verified on public resolvers, matching exactly what Railway shows):

• ALIAS @ -> bltclx4h.up.railway.app (TTL 300). Railway already shows this record green.
• • TXT _railway-verify = railway-verify=a4ae70c59233d7edd62dc5a5d75f3b4f9be12d4733fb0c8a4a2b9a1cdaac12c8 (still shows a warning even though it resolves correctly)
• • CNAME www -> 8jt6za55.up.railway.app
• • TXT _railway-verify.www = railway-verify=5fa959602ee757aa8f61d5f05f27edaf0512e694a1c51aa2660597fdc25ce729

What we tried: re-saved both domains on Oct 31 and waited 3+ hours, no change. staging.moveempire.app on the same project, same DNS provider, verified fine.

Could someone re-trigger verification and certificate issuance for these two domains? Our launch is Monday Nov 2. Thank you!