From 947e194d41ba30a0281305de298b094272653e58 Mon Sep 17 00:00:00 2001 From: Aminda Suomalainen Date: Tue, 14 May 2024 13:50:05 +0300 Subject: [PATCH] n/dns: HTTP/3 for the sake of HTTP/3 at the cost of another layer of filtering? --- n/dns.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/n/dns.md b/n/dns.md index 8aa27a7..723d53e 100644 --- a/n/dns.md +++ b/n/dns.md @@ -261,7 +261,9 @@ Use either `cloudflare-dns.com` (which doesn't have ECS) or `dns.google` _Private DNS_ server as [they have special handling](https://cs.android.com/android/platform/superproject/main/+/main:packages/modules/DnsResolver/PrivateDnsConfiguration.h) and are thus DNS over HTTPS3 instead of the usual DNS over TLS. This can be confirmed with [`https://1.1.1.1/help`](https://one.one.one.one/help) (when using -`cloudflare-dns.com`). +`cloudflare-dns.com`). **_However is connectivity in limited networks and +maybe a bit faster speed in bad network more important than a level of +security reached by a filtering resolver?_** Then setup your web browser (including Firefox (other than stable which disables `about:config`) and Chrome) to use DNS over HTTPS with your preferred