21 days ago
I have a service (habit_tracker_app) in production with deployments marked SUCCESS, but all configured service domains return SERVFAIL on DNS queries:
nslookup habittrackerapp-prod-v2.up.railway.app
** server can't find habittrackerapp-prod-v2.up.railway.app: SERVFAIL
I've tried:
- habittrackerapp-production-new.up.railway.app → SERVFAIL
- habittrackerapp-prod-v2.up.railway.app → SERVFAIL (after successful deployment ID: 65d9b6d0)
- habittrackerapp-prod.up.railway.app → SERVFAIL (after successful deployment ID: c66152d7)
Service status: Online, 1 replica running, port 8787 configured
Latest deployment: SUCCESS
This blocks all HTTP access. The service itself is healthy — the problem is DNS resolution on Railway's side.
Project: graceful-serenity
Service: habit_tracker_app
Deployment: c66152d7-906a-45f7-893f-8d23ef2cf7e0
1 Replies
21 days ago
The domain habittrackerapp-prod.up.railway.app is resolving correctly and your service is responding on it, so this is not a Railway-side DNS issue. The SERVFAIL is coming from your local DNS resolver. Try switching 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. mobile data instead of Wi-Fi) to confirm. The other two domains you listed (habittrackerapp-prod-v2 and habittrackerapp-production-new) are not configured on your service, only habittrackerapp-prod.up.railway.app exists. Note that requests reaching your app currently get a 404 because no route is defined for GET /.
Status changed to Awaiting User Response Railway • 21 days ago
14 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 • 14 days ago