Anytime you visit a website either HTTP enabled, the DNS query converts the web address to an IP address that the computer can read. This standard is implemented at the app level, making Firefox the first browser to use DNS-over-HTTPS. Encrypting the DNS query also protects the DNS request against man-in-the-middle attack.
DNS-over-HTTPS also improves browser performance and efficiency, making DNS queries and the overall browsing experience faster.
Under the laws of many countries, websites can be blocked for fueling the infringement of copyrighted or trademarked material or they are suspected to contain terrorist material or child abuse imagery. When DNS queries are encrypted they are deemed to be very difficult for ISPAs - Internet Service Provider's Association to filter their subscribers' internet access.
The ISPA is not alone, the U.K spy agency GHCQ and the Internet Watch foundation which monitors U.K's internet blocklist have also criticized the move to roll with encrypted DNS features to the browser. The ISPA doubled down on its status; ''Bringing in DNS-over-HTTPS by default would be harmful for online safety, cyber-security and consumer choice. But it encourages further debate"
Mozilla expressed its disappointment in the association for ISPs for misinterpreting an improvement to decades of old internet infrastructure. "Our goal is to build a more secure internet, and we continue to have a serious, constructive stakeholders about how to do that", they added. Mozilla isn't the first to deploy DNS-over-HTTPS. Last year Cloudfare released a mobile version of its 1.1.1.1 privacy focused DNS service to include DNS-over-HTTPS. Google also released its censorship- busting app infra which is aimed at DNS manipulation.
The date for full release of DNS-over-HTTPS in Firefox is yet to be set.