Public Railway domain not resolving (DNS_PROBE_FINISHED_NXDOMAIN)
srijan-baniyal
HOBBYOP

2 months ago

Hello everyone,

My service is deployed successfully and running correctly internally, but the public domain is still not resolving and shows the error DNS_PROBE_FINISHED_NXDOMAIN in the browser.

Public Domain:

https://personal-risk-radar-production.up.railway.app/

Service ID:

8b7b7ded-97a2-46d7-bab8-d91455b2cf9e

I have already tried accessing it in an incognito window and performed a hard refresh (Cmd + Shift + R), but the issue persists.

The Railway dashboard suggests this could be a DNS provisioning issue that requires support intervention. Could you please check the DNS provisioning for my service and help resolve the public domain issue?

Thank you.

Solved

2 Replies

Railway
BOT

2 months ago

Your domain personal-risk-radar-production.up.railway.app is resolving correctly from our side (returning an A record), so DNS provisioning is not the issue. The NXDOMAIN error is likely due to a stale DNS cache on your local device or network - try flushing your DNS cache or testing from a different network. You also have a second domain assigned to this service, personal-risk-radar-production-4b7d.up.railway.app, which you can try to confirm reachability.


Status changed to Awaiting User Response Railway 2 months ago


Status changed to Awaiting Railway Response Railway 2 months ago


sam-a
EMPLOYEE

2 months ago

Hi - I see you rejected the automated response. Was that because the domain continued not to resolve for you or because of something else?

I see the domain resolving now as well. If it was not a bad DNS lookup, it appears to have been some other transient issue. Let us know if you need more help.


Status changed to Awaiting User Response Railway 2 months ago


Status changed to Solved sam-a 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...