a year ago
Hi team,
My service is deployed and running (logs confirm server is up on port 8080).
However, my domain planmyseatbackend-production.up.railway.app returns NXDOMAIN in browser and even ping/curl fails.
I already tried deleting and regenerating the domain but the issue persists.
Please help check the DNS record and resolve the domain issue.
Pinned Solution
a year ago
If it was returning NXDOMAIN then you probably copied the domain wrong. If it was an application or DNS issue then you would be getting a different error and not NXDOMAIN.
However I do see that it's working perfectly fine when I visit it.
2 Replies
a year ago
1. Verify the Domain Exists in Railway
Go to your Railway project dashboard
Check the "Deployments" tab
Under the "Domains" section:
Confirm that planmyseatbackend-production.up.railway.app is listed as an active domain
2. Check Deployment Port
Railway expects your app to listen on process.env.PORT, not hardcoded 8080.
Your app should use:
const PORT = process.env.PORT || 8080;
app.listen(PORT, () => {
console.log(`Server is running on port ${PORT}`);
});
3. Test with DNS Lookup
Run this command:
dig planmyseatbackend-production.up.railway.app
If it returns NXDOMAIN, then the DNS record truly doesn’t exist — which means Railway hasn't provisioned the domain yet, or there’s a bug on their side.
a year ago
If it was returning NXDOMAIN then you probably copied the domain wrong. If it was an application or DNS issue then you would be getting a different error and not NXDOMAIN.
However I do see that it's working perfectly fine when I visit it.
Status changed to Solved chandrika • 12 months ago