DNS-over-TLS resolver through Tor using haproxy with built-in health checks and automatic failover.
Routes your DNS queries through the Tor network to encrypted upstream DNS resolvers. haproxy provides industrial-grade TCP proxying with native SOCKS4 support for Tor routing and active health monitoring of all upstreams.
Upstream resolvers (in failover order):
Clients connect via DNS-over-TLS — haproxy does transparent TLS passthrough, so the TLS session is end-to-end between your client and the upstream resolver.
docker run -d --name=tor-haproxy -p 853:853 --restart=always sureserver/tor-haproxy:latest
Then point your DNS client to 127.0.0.1:853 as a DNS-over-TLS upstream.
docker run -d --name=tor-haproxy --restart=always sureserver/tor-haproxy:latest
Use the container IP and port 853 as a DNS-over-TLS upstream in your resolver (Unbound, Pi-hole, etc.).
podman run -d --name=tor-haproxy -p 853:853 --restart=always sureserver/tor-haproxy:latest
| Variable | Default | Description |
|---|---|---|
PORT | 853 | Listening port (853 for DoT, 443 for DoH, 53 for DNS) |
BRIDGE1 | (built-in) | First obfs4 bridge string |
BRIDGE2 | (built-in) | Second obfs4 bridge string |
docker run -d --name=tor-haproxy \
-e BRIDGE1="obfs4 IP:PORT FINGERPRINT cert=... iat-mode=0" \
-e BRIDGE2="obfs4 IP:PORT FINGERPRINT cert=... iat-mode=0" \
--restart=always sureserver/tor-haproxy:latest
Client --[DNS-over-TLS]--> haproxy --[SOCKS4]--> Tor ---> upstream DoT resolver
fall 3 rise 2 — automatic failover to backup serverslinux/amd64 | linux/arm/v7 | linux/arm64 | linux/riscv64
MIT
Content type
Image
Digest
sha256:85139e3c9…
Size
32.4 MB
Last updated
3 days ago
docker pull sureserver/tor-haproxy