0

Issue on Android 13 - Fairphone 3 on Orange 4G network

Hello team,

I'm currently using nextDNS on my Fairphone and they just released an official Android 13 update which I installed.

However, I'm noticing that on the Orange FR 4G network some apps are either not working or some have a different behaviour.

For instance, Signal works fine, while some other apps (like Twitter but I'm not sure it's the best example at the moment)

In addition in Firefox for instance orange.fr is not reachable but bortzmeyer.org is.

Checking the logs in my nextDNS profile I see the request coming through.

As a workaround I can disable the private DNS resolver but it kinds of defeats the purpose in the first place (while at least my apps/sites are reachable)

 

Side notes:

1) it worked in my previous Android version (11)

2) I have no issue while connected over Wifi

3) I'm running an unmodified android version (i.e. "vanilla" updated version)

4) I tried fiddled with the Orange APN but it wouldn't let me (+I'm not sure what to look for as I'm not sure what the root cause is.

 

Many thanks in advance for your help, any additional troubleshooting info needed, feel free to let me know.

5 replies

null
    • chiefk60vitz
    • 9 mths ago
    • Reported - view

    First off you shouldn't be using the app you should be doing it direct do you know how to do that

      • Martheen
      • 9 mths ago
      • Reported - view

      chiefk60vitz OP already mention they're using Private DNS, which is the native Android implementation, *not* app. What is your "direct" method?

      • Adrien_G
      • 9 mths ago
      • Reported - view

      just to clarify

       said:
      they just released an official Android 13 update

       here I'm talking of the Fairphone team and the update to bump the OS to Android 11 to 13
      I'm not using the NextDNS app as I explain afterwards

      Sorry for the confusion I might have caused :)

    • Martheen
    • 9 mths ago
    • Reported - view

    If you have a computer ready, try installing dnslookup from github and compare the resolution of the problematic website with your NextDNS DoT endpoint versus a generic resolver like Google & Cloudflare, using a hotspot from your phone. Also test if the problem persists when you're using other DoT providers, adblocking or not.

    It's possible that the resolved IP is different, either from ECS (you can toggle it in the NextDNS setting) or just the nameserver of the website itself that gives a different result to your mobile ISP, which happens to be unreachable from your mobile ISP. If other DoT providers also failed, try using DoH through Intra or NextDNS's own app, unfortunately, that way you can't use a VPN simultaneously.

      • Adrien_G
      • 9 mths ago
      • Reported - view

      Thanks for the suggestions I'll give them a try at least it will help discarding various things!
       

Login to reply

Content aside

  • 9 mths agoLast active
  • 5Replies
  • 170Views
  • 3 Following