a month ago
I'm experiencing a persistent DNS resolution issue. My deployment shows as "Active" and logs confirm the server is running successfully, but all generated domains return DNS_PROBE_FINISHED_NXDOMAIN errors.
Issue:
- Deploy logs show: "Server running on 0.0.0.0:8080"
- Database connects successfully: "The database is already in sync with the Prisma schema"
- Deployment status shows "Active" and "Online"
- But the domain returns: DNS_PROBE_FINISHED_NXDOMAIN
multiple Domains tried (all fail with same DNS error):
Steps I've taken:
1. Deleted and regenerated domains multiple times
2. Created a completely new Railway project
3. Verified Public Networking is enabled
4. Cleared browser DNS cache and flushed system DNS
5. Tested from multiple browsers and devices
Project Details:
- Build: Docker
- Server binds to 0.0.0.0:8080
- Region: us-west2
The server is clearly running (I can see API activity in logs), but traffic isn't being routed to the container. This appears to be a Railway networking/DNS provisioning issue.
2 Replies
a month ago
So DNS_PROBE_FINISHED_NXDOMAIN is unrelated to deployment being successful. It generally means the domain name itself doesnt exist in DNS
Can you confirm following -
- the domain is attached to the correct service in your project? (if there are multiple services)
- the PORT variable of the service is set to 8080?
heimdall
So DNS_PROBE_FINISHED_NXDOMAIN is unrelated to deployment being successful. It generally means the domain name itself doesnt exist in DNSCan you confirm following - - the domain is attached to the correct service in your project? (if there are multiple services)- the PORT variable of the service is set to 8080?
a month ago
DNS means the record can't be found. Changing the port won't fix this issue.
To OP:
Have you tried clearing your local DNS cache and/or setting your browser's DNS server to 1.1.1.1?
If that doesn't work, I'd try accessing the URL on a different network or check out your DNS/firewall settings.
