
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?
-
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.
-
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" }
-
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.
-
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.
-
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.
-
Work fine with 9xxxxx4.d.adguard-dns.com to.