
Same for DNS over HTTPS, remove the 'DNS-over-TLS' component. If you want to use DNS over TLS only, then the 'DNS-over-HTTPS proxy' component should be removed.

When AdGuard DNS or Cloudflare Internet safety services are enabled, only the DNS queries from devices that are not registered to use the filter profile (that is, from devices which are using a 'No filtering' profile) will be sent to specified DoT/DoH servers over an encrypted connection. The DNS servers received from your ISP and/or manually registered DNS servers will not be used. NOTE: Important! When the DoT/DoH protocol is enabled, all incoming DNS queries will be sent to the server address specified during the configuration. Below, we will guide you to encrypt your DNS traffic, as sent over the router, by default. Starting with version 3.1, KeeneticOS supports DNS over TLS and DNS over HTTPS protocols. There are also lists of public DNS services that support DoT/DoH: Information on how DoT and DoH work can be found on the following pages:

We won't cover the theory in detail in this article. Special DNS protocol extensions, DNS over TLS (DNS over TLS, or DoT, RFC7858) and DNS over HTTPS (DNS over HTTPS, or DoH, RFC8484) are developed to ensure the security of DNS traffic. Their main purpose is to encrypt DNS traffic to prevent interception and provide additional privacy and security. ISPs can monitor traffic and collect data about what sites you visit. DNS traffic is vulnerable to cybercriminals as there is an opportunity to 'eavesdrop' on the communication channel and intercept unprotected personal data. As we know, the DNS (Domain Name System) protocol does not encrypt requests, and data is transmitted openly.
