A docker container which runs the cloudflared proxy-dns at port 54 based on alpine with some parameters to enable DNS over HTTPS proxy for pi-hole based on tutorials from Oliver Hough and Scott Helme

Replace amd64 most normal PC's with arm64 or arm for RaspberryPi, BananaPi etc.

Port 54 on host network so every device on the network can reach the Proxy

docker run -it --rm --name cloudflared --net host knight/cloudflared-dns:amd64

dig example.com @IP_OF_HOST -p 54

If you stop this container it will remove itself!

You can set up this Host to be a normal DNS resolver. You can put the Host IP into every client like with 1.1.1.1 or 8.8.8.8 or inside your router so you do not need to do it manually.

Examples: Lifewire, The Verge

docker run -d --name cloudflared --restart=always -p 53:54/udp knight/cloudflared-dns:amd64

Install Docker curl install.docker.com | sudo bash and Pi-hole

docker run -d --name cloudflared -p 127.0.0.1:54:54/udp --restart=always knight/cloudflared-dns:amd64

Enter IP 127.0.0.1#54 into Custom 1 (IPv4) within the Pi-Hole Admin Page

You can see the build, it's status and the push to Docker Hub on Travis-CI I run it every week so that there is no bug in it from the upstream apline image.

Issues, Pull Requests and Wiki additions are very welcome 😊

I wrote some tests in a goss.yaml file which can be executed by dgoss

$ dgoss run --name cloudflared --rm -ti knight1/cloudflared:latest
INFO: Starting docker container
INFO: Container ID: e5bd35d3
INFO: Sleeping for 0.2
INFO: Running Tests
Process: cloudflared: running: matches expectation: [true]
Package: ca-certificates: installed: matches expectation: [true]
Command: cloudflared --version | head -1: exit-status: matches expectation: [0]
Command: cloudflared --version | head -1: stdout: matches expectation: [cloudflared version DEV (built unknown)]


Total Duration: 0.028s
Count: 4, Failed: 0, Skipped: 0
INFO: Deleting container

MIT Licensed (file LICENSE).