
Is JioFiber blocking or breaking Railway.app PaaS DNS resolution in India?
I ran into a weird issue today with my Railway deployment and after debugging for hours, it looks like the problem may actually be JioFiber DNS.
My app domain:
`https://Z\*\*\*\*i-production.up.railway.app\`
Problem:
* Railway dashboard showed the domain correctly
* Deployment was healthy
* Public DNS resolvers worked
* But browser + system DNS on JioFiber failed
This failed:
```powershell
nslookup Z****i-production.up.railway.app
```
Output:
```powershell
*** reliance.reliance can't find Z****i-production.up.railway.app: Query refused
```
But these worked perfectly:
```powershell
nslookup Z****i-production.up.railway.app 1.1.1.1
nslookup Z****i-production.up.railway.app 8.8.8.8
```
Both resolved correctly to Railway IPs.
The second I enabled Cloudflare WARP everything started working instantly.
So now I’m wondering:
* Is JioFiber filtering/blocking Railway domains?
* Is this some IPv6 resolver issue on Reliance DNS?
* Is Railway’s DNS propagation incompatible with some Indian ISPs?
* Anyone else facing this with Railway.app, Vercel, Render, Fly.io, etc?
Would love to know if others in India are seeing the same issue.