0

NextDNS Blocklists not working on cellular

When I connect our phones to NextDNS on our home wifi network, ads are blocked and certain websites are blocked (for example, troypoint.com gives a connection reset error). This is what I want with the blocklists I've selected. Our wifi router is set up to use NextDNS using the instructions for IPv4 at https://my.nextdns.io.

When I use our phones on our cellular mobile network, ads are no longer blocked in some apps, and troypoint.com is easily reachable. (Not to single out troypoint.com but I finally found a good test case.)

On both networks, https://my.nextdns.io says "All good! This device is using NextDNS with this profile" even though the Linked IP is different.

Confirmed the same behavior with both Android and iPhone, wifi and cellular (AT&T).

 

How can I get NextDNS working on cellular? Seems as if our phones are bypassing the blocklists somehow and just using AT&T for DNS.

3 replies

null
    • Calvin_Hobbes
    • 1 yr ago
    • Reported - view

    Your cellular connection doesn’t use your router.   You’ll need to install NextDNS on your mobile devices if you want NextDNS to work on cellular connections 

      • Randomize
      • 1 yr ago
      • Reported - view

       Yes, I forgot to mention that I have my Android phone set up to use "Private DNS" per the instructions under the Setup Guide for Android. In my case it tells me to enter <6 char config ID>.dns.nextdns.io, which I've done.

      On iPhone I've installed the NextDNS app and entered the same 6 characters.

      I know that part is working because of the "All good! This device is using NextDNS with this profile" message.  The mystery is why NextDNS isn't blocking anything on cellular. Any ideas?

      • Randomize
      • 1 yr ago
      • Reported - view

      What is the a recommended way to get tech support for this issue? I don't mean this to sound cranky, but in a nutshell NextDNS is not doing what I bought it to do: provide DNS filtering both in and out of the home. If there is no solution I may need to look at other options for DNS.

Content aside

  • 1 yr agoLast active
  • 3Replies
  • 219Views
  • 2 Following