Having looked into this, the issue appears to be in your application code or configuration rather than the Railway platform itself, which puts it outside what Railway support can resolve directly.

This is exactly the kind of problem the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

• Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
• Keep it private and close the thread - Nothing becomes public. The thread closes, since this isn't something Railway support can take further.

Is there any other workaround? My client's team manages the DNS configuration, and I'd rather not ask them to re-add or modify the DNS records since they've already confirmed everything is configured correctly.

Unfortunately, no.

check using intodns and it will help detect your issue.

Also open to any other solutions if anyone's run into this before, updated the details above with what I've tried so far.

Did you try removing the domain and re adding it?

Before I do anything on my end, I want to first understand why this is happening, since my client manages the DNS. I want to make sure this doesn't come back for all three services again once it's fixed.

Sometimes, the DNS validation gets stuck, and the only option is to remove and re-add the domain.

Once a domain is verified with TLS cert. It would be a permanent fix unless you add any other new custom domain.

But that's the point, why did it get stuck even after adding the correct records? This reduces client reliability, and Railway should be responsible for that

It didn't stuck. It takes a few hours (maybe even a day) for railway to validate your DNS records. If it did, removing and re adding the domain would instantly fix that.