Railway-generated domains repeatedly return DNS_PROBE_FINISHED_NXDOMAIN.
rushpay0-eng
FREEOP

2 months ago

Environment: production

Current domain: worker-production-48b6.up.railway.app

Target port: 8080

Deployment status: Online

I regenerated multiple public domains, updated PUBLIC_URL, redeployed, and tested on different networks. Please check DNS provisioning for this service.

Screenshot_2026-07-26-13-06-58-08_40deb401b9ffe8e1df2f1cc5ba480b12.jpg

Attachments

Solved

1 Replies

Railway
BOT

2 months ago

Your current domain worker-production-48b6.up.railway.app is resolving correctly and returning a 200 response from our edge. The NXDOMAIN in your screenshot is for worker-production-7da4.up.railway.app, which is a previously regenerated domain that no longer exists. When you regenerate a service domain, the old one is removed and only the latest one works. If the current domain also returns NXDOMAIN on your device, your DNS resolver is likely filtering *.up.railway.app. Switching to a public resolver like Cloudflare (1.1.1.1) or Google (8.8.8.8) and flushing your DNS cache will resolve that.


Status changed to Awaiting User Response Railway • 2 months ago


Railway
BOT

2 months 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 • 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...