4 hours ago
Hello Railway Support,
I'm experiencing a private networking DNS resolution issue between my Node.js E-DTR service and MySQL service.
Both services are in the same Railway project and Production environment.
Details:
- MySQL service status: Online
- MySQL deployment: Successful
- E-DTR service: Private Networking enabled
- MySQL service: Private Networking enabled
- Both endpoints show "Ready to talk privately."
MySQL private domain:
mysql.railway.internal
E-DTR private domain:
egm-personal-e-dtr.railway.internal
However, the E-DTR application consistently returns:
getaddrinfo ENOTFOUND mysql.railway.internal
Railway DNS logs also show NXDOMAIN for both A and AAAA lookups of mysql.railway.internal.
Could you please investigate whether the MySQL private networking endpoint is properly registered and has assigned private IP addresses in our Production environment?
Thank you.
1 Reply
4 hours ago
Your MySQL service and your E-DTR service are in two different projects, not the same one, which is why mysql.railway.internal returns NXDOMAIN from the E-DTR service.
The private network is isolated per project and environment, so services in different projects cannot resolve or reach each other over railway.internal, even when both show private networking enabled. For the E-DTR service to reach MySQL privately, both services need to be in the same project and environment. More detail is in How Private Networking Works.
Status changed to Awaiting User Response Railway • about 4 hours ago