a month ago
Hi Railway team,
I'm seeing a DNS resolution issue that appears to affect Jio DNS specifically.
Project:
- Service: hayaty-backend
- Public domain:
https://hayaty-backend-production.up.railway.app
The deployment is healthy.
Deployment logs:
- Gunicorn running
- Listening on 0.0.0.0:8080
HTTP logs work correctly whenever the domain resolves.
Testing results:
✓ Google DNS (8.8.8.8)
nslookup hayaty-backend-production.up.railway.app 8.8.8.8
Returns:
69.46.46.25
✓ Cloudflare DNS (1.1.1.1)
Returns:
69.46.46.25
✗ Jio DNS
Default Jio resolver returns NXDOMAIN / Query Refused.
The same happens on multiple Jio devices.
Additional evidence:
- If I manually change the phone DNS to Google DNS or Cloudflare DNS, my app immediately works.
- If I switch back to the default Jio DNS, the app immediately fails.
- When using Jio DNS, Railway HTTP logs show absolutely no incoming requests, meaning the request never reaches Railway.
This doesn't appear to be a deployment issue because the backend is healthy and works perfectly when using another DNS resolver.
Could you please check whether this Railway-generated domain has any DNS issue with certain ISP resolvers (especially Jio), or whether there is anything on the Railway side that could cause this?
Thank you.
4 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Try using a VPN or a custom domain. Seems like the ISP is blocking traffic to Railway’s pregenerated URLs.
0x5b62656e5d
Try using a VPN or a custom domain. Seems like the ISP is blocking traffic to Railway’s pregenerated URLs.
a month ago
Thank you.
I tested further and it appears to be a DNS resolution issue rather than traffic being blocked.
The same Jio connection works immediately if I manually change only the DNS resolver to Google (8.8.8.8) or Cloudflare (1.1.1.1).
Using the default Jio DNS:
- Browser shows DNS_PROBE_FINISHED_NXDOMAIN.
- nslookup fails.
- Railway HTTP logs receive no requests.
Using Google DNS or Cloudflare DNS:
- The same domain resolves correctly.
- The app works immediately.
- Railway HTTP logs show requests.
Would this indicate an issue with how this Railway-generated domain is being resolved by certain ISP DNS resolvers?
Thanks.
raheezz
Thank you. I tested further and it appears to be a DNS resolution issue rather than traffic being blocked. The same Jio connection works immediately if I manually change only the DNS resolver to Google (8.8.8.8) or Cloudflare (1.1.1.1). Using the default Jio DNS: - Browser shows DNS_PROBE_FINISHED_NXDOMAIN. - nslookup fails. - Railway HTTP logs receive no requests. Using Google DNS or Cloudflare DNS: - The same domain resolves correctly. - The app works immediately. - Railway HTTP logs show requests. Would this indicate an issue with how this Railway-generated domain is being resolved by certain ISP DNS resolvers? Thanks.
a month ago
DNS resolution is still being blocked by your ISP.
There have also been threads created by other users stating how their ISP blocked resolution to Railway’s pregenerated domains.
Your options are to use a different DNS server or to use a custom domain.
0x5b62656e5d
DNS resolution is still being blocked by your ISP. There have also been threads created by other users stating how their ISP blocked resolution to Railway’s pregenerated domains. Your options are to use a different DNS server or to use a custom domain.
a month ago
so its better for me to buy a domain for this ?