"Do DNS resolves over HTTPS for privacy, performance and security. Also makes it easier to use a name server of your choice instead of the one configured for yo

"Do DNS resolves over HTTPS for privacy, performance and security. Also makes it easier to use a name server of your choice instead of the one configured for your system." "A server that is acting both as a normal web server and a DNS API server is in a position to choose which DNS names it forces a client to resolve (through its web service) and also be the one to answer those queries (through its DNS API service)." https://tools.ietf.org/html/draft-ietf-doh-dns-over-https-02 https://tools.ietf.org/html/draft-ietf-doh-dns-over-https-02 How might this affect users who block ads via DNS? What about users who want the system DNS settings they have configured (e.g. /etc/resolv.conf) to be honoured? I can clear browser DNS cache with a couple of keystrokes, but I am not using Chrome, Firefox, IE/Edge, Safari, Brave, Opera, etc. How easy is it for a user to clear the DNS cache in the popular browsers? The best "privacy, performance and security" for the user is achieved by using /etc/hosts. HOSTS (i.e., no DNS) will beat DNS on all three, every time. "Flexibility" was not mentioned as a criteria. There is also the issue of "transparency" to consider. It is easy for the user to check their HOSTS file to see what are the current name to address mappings. How easy is it for the user to check what mappings are in the browsers DNS cache? Fact: Many/most of the names looked up by a user repeatedly every day do not change by the hour, by the day, the week, month or even year. As a user, I use HOSTS heavily, with appropriate ed scripts for fast automated modification. I use HOSTS for the transparency, control and speed. Any privacy or security benefit is a bonus. Contrast: https://en.wikipedia.org/wiki/Fast_flux https://en.wikipedia.org/wiki/Fast_flux (need DNS or perhaps "DOH" for this to work)