3 hours ago
My Sunvale School Management System is deployed successfully on Railway, but its public domains are not resolving.
The deployment completes successfully, all Django migrations are applied, and Gunicorn starts listening on port 8080.
However, when I open my Railway public domains, I get the error DNS_PROBE_FINISHED_NXDOMAIN.
I have tried different internet connections and renamed one of the Railway domains, but the problem persists.
This is an important school management system containing student records, admissions, fees, attendance and other school information.
Please investigate the DNS issue and help me restore access to my application. I would also appreciate guidance on how to safely preserve my existing database and persistent volume while I arrange to migrate to another hosting provider.
1 Replies
3 hours ago
Your public domain resolves correctly from the public internet and is answered by our edge, so DNS_PROBE_FINISHED_NXDOMAIN means the DNS resolver your device is using is not returning our record. Try switching your device or router to a public resolver such as Cloudflare (1.1.1.1) or Google (8.8.8.8), flush your local DNS cache, and test from a different network such as mobile data. Different Wi-Fi networks or devices behind the same ISP or router DNS can all fail the same way.
Once the name resolves, the application currently answers our test request with an HTTP 400, so the app itself may also need attention after DNS is sorted.
To preserve your data, both your app service and your Postgres service have volumes attached, and you can create manual backups or set daily, weekly or monthly backup schedules from each service's Backups tab, as described in our backups guide. Files on a volume can also be downloaded with the CLI using railway volume files download, covered in the volumes guide.
Status changed to Awaiting User Response Railway • about 3 hours ago