Hello Railway Support, I have an active deployment named "customer-scoring". The deployment status is successful and active, but the public domain is not working: https://customer-scoring-production.up.railway.app Issue: * Browser shows: DNS_PROBE_FINISHED_NXDOMAIN * nslookup cannot resolve the hostname * Deployment is active and healthy in Railway * Public networking is enabled and the domain is attached to port 3000 Could you please check whether the DNS record for this Railway domain has been provisioned correctly or if there is an issue with the assigned domain? Thank you.

domain not working - Railway Central Station

domain not working

subir1910

PROOP

19 days ago

Hello Railway Support,

I have an active deployment named "customer-scoring".

The deployment status is successful and active, but the public domain is not working:

https://customer-scoring-production.up.railway.app

Issue:

Browser shows: DNS_PROBE_FINISHED_NXDOMAIN
nslookup cannot resolve the hostname
Deployment is active and healthy in Railway
Public networking is enabled and the domain is attached to port 3000

Could you please check whether the DNS record for this Railway domain has been provisioned correctly or if there is an issue with the assigned domain?

Thank you.

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • 19 days ago

0x5b62656e5d

MODERATOR

19 days ago

Try clearing your local DNS cache, changing networks/devices, or using 1.1.1.1 as your DNS server.

angelo-railway

EMPLOYEE

17 days ago

Hi Subir — I checked customer-scoring-production.up.railway.app from our side and Railway's DNS for it is provisioned and resolving correctly worldwide (it resolves to 69.46.46.27 from public resolvers including 1.1.1.1, the edge is serving it with a valid TLS cert, and requests reach your app and return a 404 on the root path). So there's no provisioning issue on our end.

DNS_PROBE_FINISHED_NXDOMAIN with a working global record almost always means your local network or resolver is the bottleneck. A few things to try:

Switch your DNS to 1.1.1.1 or 8.8.8.8.
Flush your local DNS cache: macOS sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, Windows ipconfig /flushdns.
Try a different network (mobile hotspot) or device to rule out a captive/ISP resolver.
The 404 on the root is just because your app isn't serving /; your actual routes are reachable.

If it still fails after switching resolvers, share the output of dig @1.1.1.1 customer-scoring-production.up.railway.app from your machine and we'll dig further.

Status changed to Awaiting User Response Railway • 17 days ago

Railway

BOT

10 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 10 days ago

Welcome!