n/dns: HTTP/3 for the sake of HTTP/3 at the cost of another layer of filtering?

This commit is contained in:
Aminda Suomalainen 2024-05-14 13:50:05 +03:00
parent c6d5a35123
commit 947e194d41
Signed by: Mikaela
SSH Key Fingerprint: SHA256:CXLULpqNBdUKB6E6fLA1b/4SzG0HvKD19PbIePU175Q
1 changed files with 3 additions and 1 deletions

View File

@ -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 _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 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 [`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 Then setup your web browser (including Firefox (other than stable which
disables `about:config`) and Chrome) to use DNS over HTTPS with your preferred disables `about:config`) and Chrome) to use DNS over HTTPS with your preferred