DNS-DoH-companion
A lightweight DNS server that forwards your network's DNS queries over DNS-over-HTTPS (DoH) to a provider of your choice.
Platform availability
Available on 2 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
83/100 Excellent
- Maintained
- 100last commit 29 days ago
- Popular
- 8313,797 GitHub stars
- Easy to install
- 452 install platforms, install notes, Docker image
- Light to run
- No data
- Security check
- 85no serious findings, CI, tests, OpenSSF Scorecard 6.3/10
Based on 4 of 5 factors.
Availability: platform listings confirmed today, links checked 35 days ago
- GitHub stars
- 13,797
- Open issues
- 7
- Last commit
- 2026-10-22
- Latest release
- 2.1.20
- License
- ISC
- Activity
- rising
Checked 21 days ago - source: GitHub (DNSCrypt/dnscrypt-proxy)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Install the Azure DNS resolver module If you will use PowerShell to set up Azure DNS, install the Az.DnsResolver module (a set of Azure DNS commands) after installing the Az module. Without it, PowerShell will not recognize the resolver commands and setup will fail. source
- Check DNS with ping after setup After your setup is running, ping a name that should resolve, such as myvm01.private.contoso.com. If you see replies, DNS is working; if not, the DNS record, resolver, or network path is misconfigured. source
- Assign an IP or remap port 53 Before running, give the container a fixed IP on a macvlan bridge, or expose host port 53 to another port on a normal bridge; the container will not start without one. source
Fetched 38 days ago - each note links to its source
Variants
Alternatives (11)
- Amazon Web Services - A pay-as-you-go cloud computing platform with services in networking, compute, storage, and IoT, accessible via global server farms.
- Anubis - Anubis is a lightweight, self-hosted web firewall that weighs each incoming connection with a proof-of-work challenge before it reaches you…
- BunkerWeb - BunkerWeb is a self-hosted, open-source web application firewall and NGINX-based web server that protects services with secure-by-default s…
- Cisco Umbrella - Cisco Umbrella (formerly OpenDNS) provides the first line of defense against threats on the internet wherever users go.
- Corvus - Self-hosted reverse proxy and web application firewall with a web console; it provides domain forwarding, free SSL, live traffic monitoring…
- CrowdSec - CrowdSec is a free, open-source IDS/IPS and WAF that detects malicious behavior by analyzing server logs and HTTP requests, then blocks off…
- DNS4EU
- DeCDN Node - deCDN Node is the daemon that runs a deCDN cache node — bond funds, serve cached content, and get paid per megabyte — deployed on Kubernete…
- DigitalOcean - Cloud computing platform with Droplets for virtual servers, managed Kubernetes, spaces for storage, and managed databases aiming at develop…
- Duck DNS - Free dynamic DNS hosted on Amazon VPC.
- Haproxy - HAProxy is a TCP proxy and a HTTP reverse proxy.
Checked 40 days ago - source: AlternativeTo
Common questions
Should I check for a local port 53 conflict before running the DNS service?
Yes, make sure nothing else is running on localhost:53, because port 53 is the standard DNS port.
What happens if my upstream DoH provider is blocked?
A self-hosted DoH server still needs a way to communicate with an upstream DNS server, so resolution can fail if both regular UDP DNS and DoH are blocked.
How can I verify DNS-DoH-companion is resolving correctly after setup?
Ping a name that should resolve. If you get replies, DNS is working; otherwise the resolver, record, or network path is misconfigured.
What redundancy should I consider if I self-host DNS for the whole network?
Use at least two instances on different subnets or IP ranges, and ideally host them in separate cloud providers to reduce risk.
Answers sourced from developers.cloudflare.com, learn.microsoft.com, www.reddit.com, www.reddit.com
Community
- Self hosted DoH : r/selfhosted - Reddit (reddit)
- DNS-over-HTTPS (DoH) FAQ : r/firefox - Reddit (reddit)
- doh testing | Windows Forum (forum)
- DNS, DoH, DoT, DoQ, DNSCrypt, DNSSEC - Privacy and Filtering (forum)
- Questions regarding DoT/DoH : r/dns - Reddit (reddit)
- Easy way to self host DNS : r/selfhosted - Reddit (reddit)
Collected 49 days ago - public community threads