Your deployment is healthy and the service domain resolves correctly on our side, returning a 200 response. DNS_PROBE_FINISHED_NXDOMAIN on a Railway-generated .up.railway.app domain means your local DNS resolver is failing to resolve the hostname, not that anything is wrong with the service itself. Try switching your device or router DNS to a public resolver like Cloudflare (1.1.1.1) or Google (8.8.8.8), flush your local DNS cache, and test from a different network (e.g. phone on mobile data) to confirm whether the issue is specific to your current network's DNS.

Its working on mobile but in laptop its not working i try with different laptops with different internet connection even with mobile hotspot

Try to use cloudflare's DNS resolver 1.1.1.1 on your laptop

i have tried it and its work but when you try to open it to other machine then same problem happening, user don't go to the settings and change the DNS Service Provider, we need solid solution to overcome this issue

Unfortunately, since this is a DNS caching issue, your only options would be to either wait for the current DNS resolver used by the devices you mentioned to pick up the new domain (it can take up to 72 hours at most), or you change your DNS resolver as a workaround like I mentioned above. There isn't anything else that can be done in this case.

Maybe you can try running ipconfig /flushdns in a terminal in your pc.

Sometimes if you try to access the site before it's done "spreading" you'll get that error, at least it happened to me.