2

Dear NextDNS, Loved your service till today, but my DNS queries are not resolving since morning of 29 Dec, in India, Very bad experience.

732B3CBA-CEDC-4DF9-A757-9B05272D80D4

my account: privaterelayappleid@protonmail.com

9 replies

null
    • arun
    • 4 yrs ago
    • Reported - view

    Jio broadband by any chance? I submitted a similar thread here - https://help.nextdns.io/t/x2htk69

    • Rajneesh_rana
    • 4 yrs ago
    • Reported - view

    Having same issues with Jio FTTH AS55836 - Unable to reach any dns servers of NextDNS

    On Airtel and BSNL either they have same issue or are using Singapore and Hongkong servers

    https://nextdns.io/diag/5c51e690-49bd-11eb-aaee-adbaa1733145

      • arun
      • 4 yrs ago
      • Reported - view

      Rajneesh rana is this report generated when connected to Jio?

      • Rajneesh_rana
      • 4 yrs ago
      • Reported - view

      arun No this was generated on BSNL.

      On Jio the report tool fails to upload data and does not generate full report.

      • arun
      • 4 yrs ago
      • Reported - view

      Rajneesh rana assumed that might be the case on Jio. In any case, things look okay on Jio now. Could you confirm?

      • Rajneesh_rana
      • 4 yrs ago
      • Reported - view

      arun a bit better but still not usable.

      Result from ping.nextdns.io shows primary still failing and secondary going to AMS 

        gc-bom            42 ms
  do-blr            54 ms
  ls-pnq            57 ms
  microhost-del     75 ms
  anexia-hkg       115 ms
■ anexia-ams       177 ms  (secondary)
  premiumrdp-ruh   192 ms
  edis-dxb         242 ms
  anexia-dxb       268 ms
  zepto-hkg        271 ms
  premiumrdp-dxb   278 ms
■ dns1.nextdns.io   error  (primary)
    • Jsn
    • 4 yrs ago
    • Reported - view

    Having the same issue with Hathway..

      • arun
      • 4 yrs ago
      • Reported - view

      Jsn as Jio owns Hathway, looks expected.

    • Jermaine_Potts
    • 4 yrs ago
    • Reported - view

    It seems JioFiber has suddenly decided to close ports that NextDNS uses. Also, I tried using other DoT resolvers in Android PrivateDNS and they worked correctly. I used NextDNS DoT on a DNS-changer app, and even that functioned properly. But they will consistently use up the VPN profile.
    There has to be a fix. :/

Login to reply

Content aside

  • 2 Votes
  • 4 yrs agoLast active
  • 9Replies
  • 255Views
  • 5 Following