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?
-
The fix is now fully deployed
-
NextDNS after the fix announced everything was fine, but the same problem has reappeared unfortunately.
-
NextDNS I seem to have the problem back again as well. Everything has been working smoothly since the fix was deployed up until today.
-
Sea Wolf it is likely a different problem as nothing has been rolled back. What is your ISP?
-
NextDNS I'm on Telstra Australia. The issue does seem to be intermittent and specific to DoT, if I use DoH the problem isn't there.
-
NextDNS It is not working for me since day one I received my Pixel 7 with Sosh (Orange Network)... I use the nextdns application as a workaround but this is not a solution :/
-
NextDNS OK nevermind, I found the solution : resiliate my NextDNS account and slowly migrating all my devices to Adguard DNS which is working perfectly on my Pixel 7
-
-
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!
-
On second thought, is it sure it is about IPv6? when I use different IPv6 connectivity tests using default DNS, everything seems reachable, even IPv6 DNS resolvers. But switching to nextdns make all tests fail. It's a bit strange, as if NextDNS was specifically filtered. Is there a way to check that?
-
-
Hi everybody, hello tout le monde!
I have the same problem with CalyxOS on my Pixel6a. Still OK on my GraphenOS on Pixel 3XL
-
Same issue with Pixel 6 recently updated to Android 13 (the problem apparently predates this)
Consistently says "Private DNS server cannot be accessed." either with or without the App.
Works fine with WiFI, though it kind of struggled before IPV6 was enable on my network. -
Same here, Pixel 6 pro it used to work then suddenly with Nextdns app works but private DNS no, while on wifi, via mobile network works fine.
If I try one.one.one.one it works fine.
I don't think this depends on the wifi network operator, because I have configured my home router to use nextdns and all other devices work fine.
-
It's mostly Ports being blocked by the network provider. I was using Vodafone where I live and they were blocking the DoT port so I couldn't use Private DNS. So if it's working on one network like home WiFi and not on Mobile or vice versa it's likely the network blocking it.
Pretty sure I heard that T-Mobile also has issues when you have some Parental Control / Safe DNS options provided by them.
-
My wife's phone works fine with the same connection, so i doubt that it depends on the network provider.
-
-
Hi there
Only me and my family's two Pixel6a's can't reach the internet from the home network, but I think this is probably the case in our case. (IPv6 and v4 are coming to the router, wifi is a bridge)
I'll review the network to try and fix the problem.
-
I'm now experiencing this issue as well. Been using NextDNS through private DNS setting on a Galaxy S22 Ultra with Telstra in Australia. Suddenly it stopped working while on mobile date, but works fine when I'm connected to WiFi. If I use the NextDNS app I'm able to connect and if I change the private DNS setting to a different provider (ControlD, Cloudflare etc.) then it works fine, so whatever the issue is it's specific to NextDNS.
Telstra has been gradually moving to an all IPv6 network, so it's possible that I've been cutover and that's now part of the problem.
-
Sea Wolf same, on Telstra and experiencing the same problems.
-
Justin Freitag Good to know that it's not just me!
-
-
5 month and not solved?
I have the same issue on my pixel7 and its work fine with quadnine DNS...
dns.quad9.netPlease do something.
-
Gui Gast The problem is only going to keep spreading as more mobile providers move to single stack IPv6. Whatever the issue is it seems to be unique to NextDNS, I'm having trouble using ControlD instead now.
-
Sea Wolf Didnt knew ControlD, seems nice, will get a try. Thanks!
-
-
Work fine with vpn to home router configur with NextDNS.
-
Work fine with 9xxxxx4.d.adguard-dns.com to.
-
We found the issue and we have a fix waiting to be rolled out.
-
NextDNS That's great news. Glad its been tracked down, I know how frustrating it can be to locate these sort of issues.
-
-
I can confirm is working now on Pixel 7 in 4G connection!! Good job, thanks!!
-
Seems good on my pixel7 to, thanks!
-
All seems to be working again on my S22 on Telstra. :-)
-
My pixel6a is now working
Thank you! -
Hello,
What was the solution? I'm facing this exact problem on Pixel7. (DOT)
Adding: It is an intermittent issue. Usually, reproducible when changing the device connection type. (Wifi -> Mobile data)
