Jio broadband likely blocking NextDNS
I'm reaching out to report that Jio broadband (an ISP in India) is blocking NextDNS. NextDNS website and queries don't work when I'm on Jio.
Without Jio, it's fine. With NordVPN, Cloudflare's Warp, and other VPN, NextDNS is fine.
Similar thread - https://redd.it/km9inh
I can try to submit diagnostics report (from NextDNS.io/diag) later today. On mobile at the moment.
32 replies
-
Have any fix? I'm facing similar issue as well
-
I'm not too sure, but it seems to be resolved now. Could anyone confirm?
-
Issue seems to be resolved. However, I am currently connecting to the Italy or the Netherlands DNS servers instead of any Indian ones, therby increasing ping. Also when I run ping.nextdns.io, I get an error from my primary server dns1.nextdns.io which doesn't resolve. The secondary server (Netherlands) however resolves.
-
Now it's working on my phone, however it only works when I configure google dns as a primary dns in Wi-Fi advanced settings and in android setting the private dns as my nextdns configuration, certain that they're censoring the dns.
-
Lilac Hat for me everything is working fine!
-
-
Oh yeah now it's working
-
Did it work for you now?
-
not working in Jio delhi
-
dns1.nextdns.io isn't responding (from India? I think the server in Pune is down) probably why it's not working for you guys. Try dns2.nextdns.io it's fine. I don't think Jio is blocking anything here.
-
Zap Neither link shows a response on my browser. Did you mean to have these tested on Android DNS-over-TLS/private DNS instead?
-
Zap dns2.nextdns.io seems reachable from my Jio Fiber connection. But how can I set it on my nextdns config?
I tried checking on ping.nextdns.io and it automatically holds dns1.nextdns.io as the primary and ERROR written beside it. -
Jermaine Potts please send the result of a "mtr 45.90.28.0" (you might need to install mtr first). This is most likely a routing issue between Jio and the provider of this PoP. The PoP is indeed not down as it would not be reachable from other ISPs and anycast would have routed you to another PoP.
-
Olivier Poitrey I tried with another ISP too (mobile data), not Jio. Same result. YogaDNS timeout everytime. Ping.nextdns.io shows my primary server (dns1.nextdns.io) as Error and second server with 178 ms latency. Tried on multiple devices and multiple IPs. On cmd, ping 45.90.28.152 is always a timeout, but ping 45.90.30.152 is resolved(granted with 180 ms latency).
I ran the diagnosing tool an hour back and sent the report too, but unfortunately forgot to give my email address.
-
Jermaine Potts can you please run the mtr?
-
Olivier Poitrey
I ran WinMTR for the host you mentioned.
Edit - Tried ping 45.90.28.0 just now again, request timed out. -
Olivier Poitrey I have also attached for your reference : https://pastebin.com/5yjWzixQ and https://pastebin.com/9FYkdn08 for both the servers.
Jermaine Potts for YogaDNS you can do this ---> Go to configuration --> DNS Servers ---> Double click on NextDNS and then in the IP address and port just change 28 to 30 and hit enter. It would then work.
-
Gaurav Mehta Thank you for the help.
I already tried that though, and my latency skyrocketed to 180ms, and there was a visible slowdown on everyday browsing and gaming. Forced to use BlahDNS till the Jio routing issue is fixed. -
Jermaine Potts Oh ok. Luckily, when I use the official NextDNS apps for Android, mobileconfig for iOS and the official windows app all my problems are resolved. I am even now being connected to the GC-BOM server with like 4ms of ping!!!
However, dns1.nextdns.io is I think still down or being blocked by Jio. BTW did you register a complaint with Jio as well to unblock it. Link --> https://www.jio.com/en-in/contact-us#/
Maybe if everyone complains about this, they will unblock it since it is not legal (due to net neutrality in India) for an ISP to do this without a government/TRAI order.
-
Content aside
-
2
Likes
- 3 yrs agoLast active
- 32Replies
- 851Views
-
7
Following