2 months ago
Hi Railway Team,
My service is running successfully, but the generated Railway domain is not resolving.
When trying to access the domain, I get the following error:
ERR_NAME_NOT_RESOLVE
DNS_PROBE_FINISHED_NXDOMAIN
I have verified that the backend is running correctly — I can see the server logs and background tasks executing without any issues.
I have also:
- Tried accessing the domain in incognito mode
- Tried from different networks
- Regenerated the Railway domain
- Redeployed the service
However, the Railway domain still does not resolve.
It appears the DNS entry for the generated railway.app domain may not be getting created or propagated correctly.
Could you please check whether the public networking / domain binding is properly configured for this service?
Project: Medu
Generated domain: medu-production-4d97.up.railway.app
Thank you.
5 Replies
2 months ago
Your domain medu-production-4d97.up.railway.app is currently resolving correctly in DNS (returning an A record), so the NXDOMAIN issue appears to have been resolved, possibly after your domain regeneration propagated. If you are still seeing the error, try flushing your local DNS cache (e.g., ipconfig /flushdns on Windows or sudo dscacheutil -flushcache on macOS) and clearing your browser cache, as stale NXDOMAIN responses can be cached locally.
Status changed to Awaiting User Response Railway • about 2 months ago
Railway
Your domain `medu-production-4d97.up.railway.app` is currently resolving correctly in DNS (returning an A record), so the NXDOMAIN issue appears to have been resolved, possibly after your domain regeneration propagated. If you are still seeing the error, try flushing your local DNS cache (e.g., `ipconfig /flushdns` on Windows or `sudo dscacheutil -flushcache` on macOS) and clearing your browser cache, as stale NXDOMAIN responses can be cached locally.
2 months ago
Hi Team,
I am still facing the same issue.
I created a completely new Railway service and generated a fresh domain, but the problem persists.
Details:
• Backend service is running successfully
• Gunicorn workers are starting correctly
• Application is listening on port 8000
• Domain is generated successfully in Railway
However, accessing the Railway domain results in:
ERR_NAME_NOT_RESOLVE
DNS_PROBE_FINISHED_NXDOMAIN
I tested from:
• multiple networks
• different systems
• incognito mode
All show the same issue.
Since the problem persists even with a new service and new domain, it appears the Railway edge domain is not resolving publicly.
Could you please check if there is any issue with the domain provisioning or edge routing for this project?
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved darshan8922 • about 2 months ago
2 months ago
Hi Team,
I am still facing the same issue.
I created a completely new Railway service and generated a fresh domain, but the problem persists.
Details:
• Backend service is running successfully
• Gunicorn workers are starting correctly
• Application is listening on port 8000
• Domain is generated successfully in Railway
However, accessing the Railway domain results in:
ERR_NAME_NOT_RESOLVE
DNS_PROBE_FINISHED_NXDOMAIN
I tested from:
• multiple networks
• different systems
• incognito mode
All show the same issue.
Since the problem persists even with a new service and new domain, it appears the Railway edge domain is not resolving publicly.
Could you please check if there is any issue with the domain provisioning or edge routing for this project?
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Open Railway • about 2 months ago
2 months ago
up
2 months ago
I'm able to access the domain just fine.
I'd try clearing your local DNS cache, setting your DNS servers to use 1.1.1.1 .
If you're still not able to resolve the URL, I'd try adding a custom domain.
Also, I'd suspect that your ISP has a firewall certain Railway domains...
Attachments