a month ago
Project ID: 2d3e9e78-2b1d-44e0-8089-97c42c1affa0
Service: web (ID: 33cb7711-c44e-41b9-b8e7-cb8fee63725b)
Problem: Public domain not resolving (DNS_PROBE_FINISHED_NXDOMAIN) despite service running healthy
Tried: DNS flush, multiple devices/networks, service restart, domain re-creation
1 Replies
a month ago
Your service domain web-production-81570.up.railway.app is resolving correctly and returning 200 responses right now. DNS shows a valid A record, the TLS certificate is valid, and traffic is reaching your service through our edge. The NXDOMAIN you saw was likely a transient DNS propagation delay after the domain was created or re-created. If you're still seeing the error on specific devices, try flushing your local DNS cache or switching to a different DNS resolver (e.g. 1.1.1.1 or 8.8.8.8) to clear any stale negative-cache entries.
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