Configuring Control D directly in the browser, will only change your DNS resolver... in the browser. The rest of the operating system will keep using your existing DNS resolvers.
You may need to do these steps even if you configured Secure DNS directly in your OS, as some browsers use DNS-over-HTTPS, which will disregard your OS DNS resolver.
Every modern browser except Safari supports DNS-over-HTTPS. Configuration is pretty similar in all of them.
- Open browser Settings menu
- Search for "DNS"
- Open whichever menu is returned in your search
- Select Use Secure DNS or Enable DNS over HTTPS and choose Custom
- Paste your Device's unique DNS-over-HTTPS resolver into the box
The above steps will work in every browser. Some browsers require additional steps, or have their own quirks, which are listed below.
In order for Firefox to exclusively use DNS-over-HTTPS at all times, you have to perform an additional step.
Open this URL in Firefox:
about:config and press the Accept the Risk and Continue button.
Search for this setting:
network.trr.mode and then set it to the value of
You can also view the full tutorial on our blog.
If you encounter the following error, temporarily disable the Default Rule -> Redirect (or remove redirection from the Google Service). This will make this error go away, and then you can change the settings back to what they were.
This happens because when you enable DNS-over-HTTPS in MS Edge, it makes a request to google.com, which if spoofed, will be treated as a "failure condition" and show this incorrect error.
You can view the full tutorial on our blog.
Updated 11 months ago