DNS-over-HTTPS (DoH) is not exactly a new technology, and it is something that is supported by all of the big-name browsers.

Google has already implemented the privacy and security boosting feature in the Windows, macOS and mobile versions of its Chrome browser, and now the company is working to bring it to Linux.

With the platform attracting a very security-minded groups of users, the only surprise here is that it has taken Google this long to bring DoH to Chrome for Linux. Once implemented, the change means that both DNS queries and DNS responses will be securely transmitted over HTTPS. But the Linux implementation is set to differ slightly from versions of the browser for other platforms.

The reason it has taken longer for Chrome for Linux to benefit from DNS-over-HTTPS is that it makes use of Chrome’s own built-in DNS client, and this is disabled by default on Linux. This has been the case for quite some time because of Chrome’s failure to respect advanced Linux DNS configuration through nsswitch.conf, which is in turn because of the complexity and variety of Linux distributions.

The solution that the Chromium Project has come up with involves building support for the browser to read and parse DNS configuration that have been put in place. It also needs to be able to disable DNS-over-HTTPS on configurations that do not support it.

The team explains ” As Chrome’s resolver does not support changing such mechanisms or their order, Chrome’s support for respecting nsswitch.conf will be limited to detection of whether or not the configuration is a common configuration compatible with Chrome behavior”. As a fallback, Chrome will not autoupgrade to DoH or use the built-in resolver unless a DoH server is explicitly selected via Chrome configuration settings.

It is not clear exactly when DoH support will arrive in the Linux version of Chrome, but it is thought to be version 91 or 92. This means that the feature should be available for testing in a matter of weeks, and will hopefully roll out on a wider basis soon after this.