2 months ago
Description: Gateway service cannot resolve internal service names in the same project/environment. Error: Failed to resolve 'auth-service.railway.internal' [A(1), AAAA(28)] and search domain query for configured domains failed as well: [internal, railway.internal] Details: - Project ID: 5faa6ac9-9c40-4bfc-a046-57a116c6dbb1 - Environment: production - Gateway Service ID: 518ac566-3b73-47be-ada9-3b5f81e35020 - All services are in the same project and environment - Services are configured to use private network DNS names (*.railway.internal) - Frontend loads correctly but cannot reach backend APIs Affected Services: - auth-service.railway.internal - vehicle-service.railway.internal - booking-service.railway.internal - user-service.railway.internal
Pinned Solution
2 months ago
Your frontend should be reaching backend through public networking, not private. This is because the frontend is the client (or user), and they don’t have access to private networking.
2 Replies
2 months ago
Your gateway-service, auth-service, booking-service, vehicle-service, and user-service all show a FAILED deployment status, which means those services are not running and therefore not registering on the private network. DNS resolution for *.railway.internal only works when the target service has a healthy, running deployment. You'll need to get each backend service successfully deployed before the gateway can resolve their internal DNS names. For configuration details, see our private networking guide.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 2 months ago
2 months ago
Your frontend should be reaching backend through public networking, not private. This is because the frontend is the client (or user), and they don’t have access to private networking.
Status changed to Solved 0x5b62656e5d • 16 days ago