a month ago
Subject: Intermittent DNS resolution failures for Railway public domains
Hello Railway Support,
My Django application is deployed successfully and listens on port 8080. Both public domains are active:
- sunvale-school-system-production.up.railway.app
- sunvale-school-system-production-6fe0.up.railway.app
Both domains resolve through Google's public DNS and respond successfully from my computer with HTTP 302 redirects to /teacher/login/. However, multiple users on both MTN and Airtel in Uganda report that they cannot access the site and receive DNS_PROBE_FINISHED_NXDOMAIN.
I have confirmed that the domains are active, the deployment is successful, and the domain target port is 8080. Please investigate whether there could be an intermittent DNS resolution or edge networking issue affecting these public domains.
Thank you.
1 Reply
a month ago
From outside your network, your app resolves and responds normally through our edge. That means the name does exist in DNS, so an NXDOMAIN on a *.up.railway.app domain comes from the DNS resolver the user is querying, usually the ISP's own DNS server filtering or failing to answer for that domain. Your plan or deployment state can't cause it.
Affected users can confirm this by switching their device or router DNS to a public resolver such as Cloudflare (1.1.1.1) or Google (8.8.8.8), flushing their local DNS cache, or testing from a different network. If the site loads after any of those, the original network's resolver is the cause.
For users on those networks to reach the site without changing their own settings, put the app on a custom domain you control. That removes the dependency on how their ISP resolves up.railway.app.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago