Private Networking endpoints have no private IPs and internal DNS returns ENOTFOUND.

Project:

melodious-youth

Environment:

production

Network:

railway

Network ID:

21a73eae-e64f-4f5e-9427-d3b838d40686

MySQL:

Service ID: 649aac39-fa97-45c2-9579-d3be0b2f1008

Hostname: mysql.railway.internal

Endpoint ID: 635de11a-4cb9-4900-a902-3de11a307994

syncStatus: ACTIVE

privateIps: []

Backend:

Service ID: 8d82e197-4fed-46d6-9fc4-2c8da671b744

Hostname: master-gym-backend.railway.internal

Endpoint ID: b991553b-0d45-4ce2-b9f6-a8793ba485b2

syncStatus: ACTIVE

privateIps: []

MySQL deployment:

7932ba9a-d599-4427-b256-2f77d03131ae

Status: SUCCESS

Backend deployment:

fccc06f1-493e-4fdc-a790-ed8f6fdb9e2b

Status: SUCCESS

From inside the Railway backend shell:

node -e "require('dns').lookup('mysql.railway.internal',{all:true},console.log)"

returns:

ENOTFOUND mysql.railway.internal

The backend also cannot resolve:

master-gym-backend.railway.internal

I have already:

• redeployed MySQL
• • redeployed the backend
• • updated both private-network endpoint names
• • verified both services are in the same production environment/network

Both endpoints remain privateIps: [].

Please investigate/reprovision the private-network endpoints for this environment.