impossible connection of private DNS on Google pixel 6
hello, since this morning, it is impossible for me to connect to the nextdns service on my pixel 6 updated with the may patch. Is there a breakdown?
-
Bonjour, j'ai exactement le même problème mais uniquement en 4g. Pas de problème en wifi
-
Hello,
01) Could you try to be more specific about your issue
02) Have you tried doing things like https://ping.nextdns.io/ and https://test.nextdns.io (Make sure to turn off in-built DNS-over-HTTPS on browser if it supports that, e.g Vanadium, Bromite, Kiwi, Iceraven, Fennec and Mull for instance)
03) Are you using the native Google Android or an alternative such as GrapheneOS, CalyxOS or DivestOS?
(Not a support staff but you aren't really giving any details to go on for them or the community, please provide as much details as possible so the staff and community can try to help)
Note: Fellow Pixel 6 user here without any issues on GrapheneOS with Private DNS.
-
Bonjour
Téléphone Google pixel 6 Android 12 officiel
Opérateur orange France
Utilisation de la fonction native d'Android Dns privé
Voici les test
-
Hi,
I'm on a pixel 4a, most recent android 12 update, also on Orange network and I'm loosing connection from time to time, even on wifi. I need to remove private DNS and after few minutes changing back.
Thank you guys for the great work, hope this is just a passing bug.
-
Off-Topic, but beware that your device becomes EOL within 1 year and 4 months.
https://endoflife.date -> Google Pixel -> 4a
-
-
Bonjour,
Problème identique ici sur Pixel 6 également, ROM stock.
-
I've been experiencing a lot of "Can't connect to private DNS" issues on my Samsung Galaxy S21 with android 12 on it. I tried the pin site, and got a ton of errors. Any suggestions? Can I share my logs with the support staff in some way?
-
Up
-
Please try with IPv6 disabled on the device to see if it helps.
-
NextDNS do we do that on the NextDNS control settings on the website? Or on our phones somewhere? Not seeing anything mentioning that on the site.
I see IPv6 mentioned under Endpoints, but I'm not using that. I'm using the Private DNS.
To be clear, this is happening on mobile data, NOT WiFi.
-
NextDNS update - Found it deep within Settings on my phone -> Connections -> mobile networks -> Access Point Names -> edit APN. Unfortunately the entire APN screen/list of options is disabled.
-
Reony Tonneyck your ISP doesn’t provide IPv6. You can’t change anything here but switching to another ISP
-
NextDNS bonjour le problème est toujours présent après la désactivation de l'ipv6
-
Does it work with the NextDNS app?
-
NextDNS oui cela fonctionne
-
tggege what do you get for https://dns.nextdns.io/info
-
NextDNS {"locationName": "
Paris, France", "pop": "anexia-par", "rtt": 810} -
tggege This is from the android device in the failing condition?
-
NextDNS oui en ipv4
-
DynamicNotSlow I figured. No worries I'll deal with it. I noticed it gets better after turning on/off airplane mode.
-
-
Hi, I also have the same problem on a Pixel 6 Pro with GrapheneOS (stable, up-to-date), and the Orange mobile operator. I cannot disable IPv6 in APN settings.
anexia-par (IPv6) 1 ms (ultralow1)
anexia-par 1 ms (ultralow1)
virtua-par 1 ms (anycast2)
virtua-par (IPv6) 1 ms (anycast2)
netbarista-par (IPv6) 2 ms (anycast1, ultralow2)
netbarista-par 2 ms (anycast1, ultralow2)
vultr-lon 8 ms
anexia-lon (IPv6) 8 ms
zepto-lon (IPv6) 8 ms
anexia-lon 8 ms
zepto-lon 8 ms
vultr-lon (IPv6) 8 ms
zepto-mrs (IPv6) 10 ms
zepto-mrs 10 ms
anexia-mrs (IPv6) 12 ms
anexia-mrs 12 ms
zepto-bru (IPv6) 12 ms
fusa-bru 14 ms
fusa-bru (IPv6) 14 ms
zepto-bru 18 ms{ "status": "unconfigured", "resolver": "90.84.9.14", "srcIP": "2a01:cb01:2067:9413:0:3d:1d8b:fd01", "server": "netbarista-par-1" }
-
Plus, I wanted to use the NextDNS app, but it creates a VPN connection to provide DNS configuration. Android does not support using two VPNs at the same time, and I already use another VPN connection to access my home network.
According to previous posts in this thread, it looks like IP6 support by the mobile carrier is problematic. Could it be circumvented by providing alternative DoT adresses that would resolve to IP4-only or IP6-only resolvers? e.g. configid.dns4.nextdns.io and configid.dns6.nextdns.io
Thanks!
-
