Service domain DNS not resolving - requests
vis99313
HOBBYOP

a month ago

Body:

I have deployed an Express.js app on Railway (School-viehal-1 service) that is running successfully, but the service domain is completely unreachable.

Service Details:

  • Project ID: 9db839ea-875c-46e7-976b-1df8fda30c2d
  • Environment: production (866ec8e6-2f52-47c5-bd01-ad7866162b2a)
  • Service: School-viehal-1 (f7f7eef8-ff04-4a0a-80e0-176220b19d7a)
  • Domain: school-viehal-1-production-ef86.up.railway.app
  • Latest deployment: dc7f10c3-62bb-4932-9bab-3af7ad6bc788 (SUCCESS)

What's working:

  • Service is online and running
  • App logs show "Server listening" on port 8080
  • Deployment status is SUCCESS
  • No errors in logs

What's NOT working:

  • Domain DNS_PROBE_FINISHED_NXDOMAIN error on all devices (phone, tablet, desktop)
  • Private domain http://school-viehal-1.railway.internal:8080 also gives same error
  • Zero HTTP requests reaching the service (empty HTTP logs)
  • Service domain is configured correctly (port 8080 mapped)

What I've tried:

  • Cleared DNS/browser cache on multiple devices
  • Tested from different networks
  • Tested on different browsers
  • Recreated service domain with
  • Fixed scheduler blocking issue in code
  • Service redeploys successfully after code changes

This appears to be a Railway infrastructure issue with domain registration or network routing. The app is healthy but completely unreachable.

Duplicate

0 Replies

Railway
BOT

a month ago

It looks like you already have a thread open about this: DNS_PROBE_FINISHED_NXDOMAIN. We're automatically closing this one, and we'll reply to you there soon. If you have anything more to add about this topic, please post it in that thread.

Status changed to Duplicate Railway • about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...