It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.

First add lasted for a few hours after which I removed and re-added it.

It's been over 24hrs and still validating.

Try removing all associated DNS records and the domain from Railway, and add them back after ~10-15 mins. Make sure you're not putting in old records if new ones are issued.

Been 5hrs now and it's still validating.

Roughly 21hrs now and still validating. Is there another way to fix this?

Your DNS seems to be set up correctly. And, if re-adding the domain didn't help, it might be an issue with your service, since when you visit the URL you get No webpage was found for the web address. Is your service actually serving a web app? And, is the Railway generated domain working?

The railway generated URL works just fine.

Here; https://myooz.up.railway.app/

Can someone help with a way out of this issue?

Anybody please

Can you verify that the correct cname that Railway is telling you to point to is "ivd3c2x3.up.railway.app" and the verification txt record is "railway-verify=3a4b88dc151cc3c452930d5b90090976b83ac081620c6611cd9bef6898801c03". What I have found in the past is that as long as the cname and txt records point to something at Railway's infrastructure, regardless of whether it points to the correct cname or not, it often shows the tick in the domain validation in the portal so worth double checking you haven't missed any characters off the end of it etc

I copied and pasted the details as shown on my dashboard... and had to manually verify each character just to be sure there weren't any mistakes.