DNS over HTTPS (DoH) is a protocol for performing remote Domain Name System (DNS) resolution via the HTTPS protocol. It is more secure than the traditional DNS and helps protect user privacy.
To learn more about Firewalla DNS Services, here is a detailed guide: DNS Services Introduction.
How does it work?
When you type a web address or domain name into your address bar, your browser sends a request over the Internet to look up the IP address for that website. Traditionally, this request is sent to servers over a plain text connection. This connection is not encrypted, making it easy for third parties to see what website you’re about to access.
DNS over HTTPS (DoH) works differently. It sends the domain name you typed to a DoH-compatible DNS server using an encrypted HTTPS connection instead of a plain text one. This prevents third parties from seeing what websites you are trying to access.
If DNS over HTTPS is enabled on Firewalla, your device will use the DoH server even if it has its own DNS server configured.
A few important things to note:
- DoH can be slower than traditional DNS queries. (Due to encryption)
- DoH will encrypt your DNS entries. If you have network security devices beyond Firewalla, it will not be able to see the DNS requests.
- If your router maps a domain name to a local IP address, you won't be able to resolve the domain name when DoH is on.
- DNS over HTTPS only encrypts the DNS query. The destination IP address in packet headers can still expose which server/s you are talking to.
- Remember, DNS over HTTPS will only hide your queries from ISPs but NOT the DNS over HTTPS providers.
- We have seen some DoH services are not stable as normal DNS servers, if you encounter problems, please try to change the DoH provider or turn off the service and test again.
How to enable DoH?
Tap on the "More" button on the main page of Firewalla Box, or go to "Settings" -> "Features", you'll find the "DNS over HTTPS" feature. This feature is disabled by default.
To enable "DNS over HTTPS", tap on the feature, switch on the feature button. You can select which devices to apply to, and which server (Cloudflare, Google, Quad9, OpenDNS) to handle the DoH queries.
How to check DoH?
To test DNS over HTTPS, set DNS over HTTPS settings to Cloudflare only (turn others off), then visit https://1.1.1.1/help
If you see problems with the test page, please check following:
- Double-check DoH settings, and make sure only Cloudflare is checked. This test is made by Cloudflare. You can turn on other sources after the test.
- Double-check that the DNS booster is on. (If you don't know what this is, please ignore.)
- Be sure the device doing the test is being "monitored" by Firewalla and that you have included the device in the DoH "Applies to" list.
How use Custom DoH Servers
You can also add customized DoH endpoints. If you want to use a provider other than the defaults provided in the app, you can use the custom DoH server to add any DoH service you like. For example, in addition to simple, unfiltered DoH service, Cloudflare Offers DoH with Filters for Malware and another for Malware and Pornography. You can add them to Firewalla like so:
The same approach will work with OpenDNS' FamilyShield:
https://doh.familyshield.opendns.com/dns-query
Dependencies with other features:
- Family Mode may not work if DoH is on.
- DNS Booster must be turned on for DoH to work.
Comments
18 comments
Any plans to select a custom DoH server? So Users could for example use nextdns with own configuration.
Unlikely we will be supporting "any" DoH server. But supporting this one is on the roadmap for sure.
How does DoH work if you have a pihole running on the firewalla? How does it work if you have a pihole on the network (not on the firewalla)?
It won't work. DoH will encrypt all DNS traffic via HTTPS, pihole is not going to see these DNS requests.
it might be worth mentioning that DoH is categorized as "Proxy/Anonymizer" by various DNS providers and enabling DoH can conflict with some DNS filtering...
-> that's what happened to us since proxy/Anonymizer were filtered out from our OpenDNS profile... so all the requests over https to google/cloudlfare would get flagged by opendns.
Any update on NextDNS or how to configure the NextDNS CLI on the Firewalla Gold?
Ditto! PLEASE add NextDNS support. The limitations of an upstream PiHole are a real deal breaker. If youre not going to add NextDNS, please improve your built in adblocker.
It's a pity custom DoH endpoints won't be supported. CloudFlare teams is currently working over DNS and currently the only option is to use non encrypted DNS with firewalla.
Indeed, we ran into this issue as well when we realized that we can't use cloudflare team anymore with firewalla as the main gateway...
however, one can still bypass firewalla completely and just point the warp client to the team doh subdomain and the org team.
When multiple providers are selected in DOH settings, are they used in a round-robin rotation or is there a priority order?
Is there a specific recommendation for using just one vs more than one one at a time?
In terms of recommending one vs another...
until clouddlare team is properly supported, you might want o look into opendns as they allow you to customize rules and (unlike cloudflare which require infividual urls) the mapping between your network and their rule is based on your public facing IP address which you can update through a classic ddns client.
The rules allow to whitelist/blacklist themes (adult, violence, p2p...) or individual domains. They offer their service for free for non-profits and individuals.
Is there any update for NextDNS to be added to DoH? Or has this idea been abondened?
We are going to make DoH configurable. likely in 1.972 or 1.973
It sure would be handy to assign individual DOH servers to networks/devices. I know I asked about it in the past, but was curious if any headway had been made?
DoH configurable for multiple device groups would be great (instead of only one)
Is it still an issue with Family Protect not working if DOH is enabled?
bks
It is still an issue, since DoH will divert DNS away from the one used in Family Protect. But likely in the future, we will completely move family protect local, so it will be work with DoH
Some of us are still hopeful for assigning individual DOH to networks/devices/vlans....
IOT gets its own set, Kids have their own... Work, etc. The workaround for me has been a multihomed dns server on each vlan to get around Firewalla's magic, but its obviously not ideal.
Please sign in to leave a comment.