Check out ZeroNS from ZeroTier!

This repository has been archived and will not receive updates because ZeroTier now builds and supports ZeroNS, which achieves the same (or better) results to what ZeroDNS set out to achieve.

Give it a look if you want hostname-like resolution for your ZeroTier peers!

ZeroDNS ( ⚠️ This project has been archived and is unsupported.)

ZeroDNS is a CoreDNS-based Docker container that allows for name resolution of your ZeroTier peers. You should point your local machine's DNS to localhost (127.0.0.1) to enable this mapping.

Configuration

1. Create a config directory for ZeroDNS.
2. For each network you want, create an empty <network-id>.conf file in the above directory.
3. Retrieve an ACCESS_TOKEN from ZeroTier Central. You'll need to pass this as an environment variable to the container.
4. Specify a command-separated list of TLDS (defaults to only .zt). Like ACCESS_TOKEN, this will be an environment variable passed to ZeroDNS.

Usage

The docs are fairly thorough in what parameters docker needs, but you can also find those details in the docker-compose.yml or docker. Additionally, if you find any of the Docker-related configurations confusing, you should take a look at the LinuxServer.io Docs, we draw heavy inspiration from their work.

Current limitations

1. Doesn't play nicely with VPNs (tested on Mullvad, Proton, TunnelBear, PIA)
2. Needs SYS_ADMIN and NET_ADMIN capabilities.
3. Will always spawn a ZeroTier One client within ZeroDNS (CoreDNS is required).