Project: Futurenostics Web
Environment: Develop Issue
Description: Unable to establish private network connectivity between NestJS backend and Redis services.
DNS resolution is failing for internal hostnames despite both services having private networking enabled.

Service Details:

1. Backend Service: -
Name: sales-management-backend

- Region: Southeast Asia (Singapore)

- Private Domain: sales-management-backend.railway.internal

- Status: Active and running

2. Redis Service: -
- Name: Redis-Sale-Management
- Private Domain: redis-sale-management.railway.internal
- Status: Active and running

-----> Current Behavior:-

- Getting consistent DNS resolution errors: "getaddrinfo ENOTFOUND redis-sale-management.railway.internal"
- Public endpoint works successfully (nozomi.proxy.rlwy.net:25429)
- Private networking shows as "Ready to talk privately" for both services
- Both services are in the same project and environment

Steps Attempted:
1. Used full internal DNS name: redis-sale-management.railway.internal
2. Used short service name: redis-sale-management
3. Verified both services have private networking enabled
4. Confirmed both services show as properly linked in the project architecture

Error Logs:
``` [Nest] 12 - 06/19/2025, 8:13:20 PM WARN [RedisService] Error stack: Error: getaddrinfo ENOTFOUND redis-sale-management.railway.internal at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26) ```

Questions:
1. Are there any prerequisites for private networking that might be missing?
2. Is there a required delay for DNS propagation after enabling private networking?
3. Are there any additional configuration steps needed beyond enabling private networking in the service settings?

Current Workaround:
Currently using the public endpoint (nozomi.proxy.rlwy.net:25429) to maintain service operation. Any assistance in resolving this private networking issue would be greatly appreciated.