Skip to content

rootwyrm/dns_docker

Repository files navigation

dns_docker

Complete multi-platform, high performance, scalable DNS suite for use in Docker with extensive user customization.

Built for amd64, i686, arm64, and arm/v7 architectures.

CC-BY-NC-3.0


CI Status

Component Status
Build Train CI - World GitHub issues GitHub pull requests GitHub milestones
dnsdist CICD - dnsdist Docker Image Size (latest semver)
unbound CICD - unbound Docker Image Size (latest semver)
nsd CICD - nsd Docker Image Size (latest semver)

Important Reminder: systemd-resolved is cancer

systemd-resolved is cancer and a significant security risk. Banish it and anyone installing or defending it from your systems at once. Running either clients or servers in an environment with so much as a functioning systemd-resolved binary will NEVER be supported. USING SYSTEMD-RESOLVED BREAKS DNSSEC AND OTHER CRITICAL PIECES, AND WILL RESULT IN INSECURE DNS, PERIOD.

Yes, I'm beyond annoyed that I have to say this multiple times to get it to sink in. If your distribution installs systemd-resolved, your distribution actively creates a significant security risk. And therefore, is wrong.

Installation

Installation instructions are not ready at this time.

(Coming soon...ish)

On Linux / x86_64 and i686

Installation instructions are not ready at this time.

No special steps.

On Linux / arm64

Installation instructions are not ready at this time.

Must use docker-compose to ensure the correct architecture is pulled; otherwise docker will try to use the amd64 images on arm64.

Use and Licensing

dns_docker is provided under a CC-BY-NC-3.0 license to prevent abusive behavior by commercial entities.

What this means in plain English is that you are free to use dns_docker in your home or business, and you may modify it to suit your needs. Generally dns_docker is best for situations where you are in need of a high-performance and secure solution that is also capable of DNS filtering.

You may not use it in a commercial product or as any part of a service which you charge for (e.g. filtering DNS services, as a DNS resolver for cloud providers, etcetera.) You are granted a limited exception to use dns_docker where you charge for a service which relies upon DNS but where dns_docker is not directly available to customers and is not incorporated within the service itself.

If you are looking for a commercial solution, dns_docker is not the appropriate product anyways! You are looking for DNSecure, which is an entirely different beast and is specifically designed to handle hundreds of thousands of queries per second per instance. Contact me for more information on DNSecure.

dns_docker is proudly built entirely on open source products: