2

DNS-over-TLS/QUIC and DNS-over-HTTPS no longer working on Android and app has disappeared?

1) What happened to the Android app? It was useful in situations like this

2) I woke up this morning with my phone not resolving any domains. In android settings, I can only set it to automatic and let the DHCP server give it an IP. Using DNS-over-TLS/QUIC device.dns.nextdns.io doesn't work anymore and Android won't let me input DNS-over-HTTPS into that box either.

19 replies

null
    • AND
    • 2 mths ago
    • Reported - view

    https://ping.nextdns.io/ shows

     lightnode-mnl             20 ms

      premiumrdp-mnl            20 ms

      greencloud-han            21 ms

      lightnode-tpe             27 ms

      greencloud-sgn            30 ms

      lightnode-sgn             56 ms

      lightnode-han             80 ms

    ■ anexia-hkg               111 ms  (anycast2, ultralow2)

      zepto-hkg                 error

      zepto-tpe                 error

    anycast.dns1.nextdns.io error (anycast1)

    dns1.nextdns.io error (ultralow1)

    • Mistahgreen
    • 2 mths ago
    • Reported - view

    Something is definitely wrong. I'm on a Samsung Galaxy S23 Ultra and using the Android Private DNS feature like @AND. I frequently get Network has no internet access now. Error Notification and Ping screenshot attached. 

    Screenshot_20240518_115532_Brave Screenshot_20240518_114955_One UI Home
      • R_P_M
      • 2 mths ago
      • Reported - view

      What blocklists have you enabled in your configuration? Maybe one of the lists is blocking the connectivity check domain. 

      • Mistahgreen
      • 2 mths ago
      • Reported - view

      Thanks for the reply. I'm using:

      1. EasyList
      2. NSABlocklist

      3. NextDNS Ads & Trackers Blocklist

      4. Steven Black

      What's the URI for the connectivity check? I'd like to Allow List it to test then. Thanks!

      • R_P_M
      • 2 mths ago
      • Reported - view

       

      Here's two I can think of right now:

      connectivitycheck.gstatic.com
captive.apple.com

      (Some android device use the apple domain for checking too)

      • Mistahgreen
      • 2 mths ago
      • Reported - view

      Thanks. I'll try and see if that helps. Seems like many others are having similar issues. 

      • Mistahgreen
      • 2 mths ago
      • Reported - view

      I feel like this is a Samsung Device issue. I don't have any other Android device to test but a few internet searches are showing similar issues among the Samsung Community. 

      • R_P_M
      • 2 mths ago
      • Reported - view

       It might well be a Samsung issue, especially if it’s also not working with other endpoints (like you mentioned in the other thread).

    • Clemente
    • 2 mths ago
    • Reported - view

    I have a Xiaomi Redmi Note Pro and have the exact same issue.
    Why the android app is no longer available?
    Is there a way to identify traffic from any android device? I use A LOT of android device and are not able to distinguish them anymore

      • R_P_M
      • 2 mths ago
      • Reported - view

      Put the name you want to use in front of the config ID with "-" in between.

      name-abc123.dns.nextdns.io

      Just look at the end of the setup page for info about adding device identifier info to your endpoints.

      • Clemente
      • 2 mths ago
      • Reported - view

      Yes, it worked. Thank you!

    • Clemente
    • 2 mths ago
    • Reported - view

    I found a solution to have DNS request identified under Android without nextDNS app.
    Where I put my own DNS for Android to have my device identified I must put the name of the device BEFORE the DNS address replacing spaces with "--" so for example if the dns to put is abc123.dns.nextdns.io and the name I want to use for device is "My Device" I must put

    My--Device-abc123.dns.nextdns.io (note the single "-" between device name and standard dns name)

    This way I can filter the traffic from "My Device" in the main nextdns log

    Hope this could help someone else

      • Mistahgreen
      • 2 mths ago
      • Reported - view

      Are you still getting the Private DNS Server Cannot Be Accessed Error?

      • Clemente
      • 2 mths ago
      • Reported - view

       

      No, it is working now

    • xor.1
    • yesterday
    • Reported - view

    @nextdns, is an updated Android app in the roadmap? It would be great to have a new Android app that supports both Doh3 and DoQ.

      • blue_rouge_62
      • yesterday
      • Reported - view

       I still have the Android NextDNS app I downloaded from Play store 5 months ago. It works fine. Let me see if its sill there......

      • blue_rouge_62
      • yesterday
      • Reported - view

       Yes the NextDNS app is still in the Google Play store. It can be downloaded from Github, where it's produced: https://github.com/doubleangels/NextDNSManager, and F-Droid. Try Doubleangels for problems. They are the developers.

      • blue_rouge_62
      • yesterday
      • Reported - view

       I'm on Samsung UI6 - Android 14 too.

Login to reply

Content aside

  • 2 Likes
  • 14 hrs agoLast active
  • 19Replies
  • 542Views
  • 7 Following