Earlier quoted context omitted.
Private DNS on Android refers to 'DNS over HTTPS' and would normally only accept a hostname. Normal DNS can normally be changed in your connection settings for a given connection on most flavours of Android.
No, it is not DNS over HTTPS it is DNS over TLS, which is different.
Cloudflare 1.1.1.1 Incident on July 14, 2025
171–180 of 391 posts
Re: Cloudflare 1.1.1.1 Incident on July 14, 2025
#172Earlier quoted context omitted.
Private DNS on Android refers to 'DNS over HTTPS' and would normally only accept a hostname. Normal DNS can normally be changed in your connection settings for a given connection on most flavours of Android.
Its DNS over TLS. Android does not support DNS over HTTPS except Google's DNS
Re: Cloudflare 1.1.1.1 Incident on July 14, 2025
#173Interesting to see that they probably lost 20% of 1.1.1.1 usage from a roughly 20 minute incident. Not sure how cloudflare keeps struggling with issues like these, this isn't the first (and probably won't be the last) time they have these 'simple', 'deprecated', 'legacy' issues occuring. 8.8.8.8+8.8.4.4 hasn't had a global(1) second of downtime for almost a decade. 1: localized issues did exist, but that's really the…
There's more to DNS than just availability (granted, it's very important). There's also speed and privacy. European users might prefer one of the alternatives listed at https://european-alternatives.eu/category/public-dns over US corporations subject to the CLOUD act.
Re: Cloudflare 1.1.1.1 Incident on July 14, 2025
#174Earlier quoted context omitted.
Just pair 1.1.1.1 with 9.9.9.9 (Quad9) so you have fault tolerance in terms of provider as well.
Windows 11 does not allow using this combination
Re: Cloudflare 1.1.1.1 Incident on July 14, 2025
#175Earlier quoted context omitted.
What would be a good reason to switch back from Google DNS?
After trying both several time I since stayed with google due to cloudflare always returning really bad IPs for anything involving CDN. Having users complain stuff take age to load because you got matched to an IP on opposite side of planet is a bit problematic especially when it rarely happen on other dns providers. Maybe there is a way to fix this but I admit I went for the easier option of going back to good old 8…
https://developers.cloudflare.com/1.1.1.1/faq/#does-1111-sen...
I've also changed to 9.9.9.9 and 8.8.8.8 after using 1.1.1.1 for several years because connectivity here is not very good, and being connected to the wrong data center means RTT in excess of 300 ms. Makes the web very sluggish.
Re: Cloudflare 1.1.1.1 Incident on July 14, 2025
#176Re: Cloudflare 1.1.1.1 Incident on July 14, 2025
#177Re: Cloudflare 1.1.1.1 Incident on July 14, 2025
#178Earlier quoted context omitted.
There's more to DNS than just availability (granted, it's very important). There's also speed and privacy. European users might prefer one of the alternatives listed at https://european-alternatives.eu/category/public-dns over US corporations subject to the CLOUD act.
HN users might prefer to run their own. It's a low maintenance service. It's not like running a mail server.
Re: Cloudflare 1.1.1.1 Incident on July 14, 2025
#179Re: Cloudflare 1.1.1.1 Incident on July 14, 2025
#180 all-servers
server=8.8.8.8
server=9.9.9.9
server=1.1.1.1