Deployment

dnsweaver is designed for containerized deployments. This section provides production-ready configurations for various environments.

Deployment Options

• Docker Compose

  ---

  The simplest deployment for single-host environments. Recommended for getting started.

  Docker Compose

• Docker Swarm

  ---

  Production deployment for multi-node clusters with high availability considerations.

  Docker Swarm

• Split-Horizon DNS

  ---

  Configure internal and external DNS records from the same container labels.

  Split-Horizon

Quick Comparison

Feature	Docker Compose	Docker Swarm
Complexity	Simple	Moderate
High availability
Secrets management	File-based	Native secrets
Best for	Development, single-host	Production, multi-node

Common Requirements

Regardless of deployment method, dnsweaver needs:

1. Docker socket access — To watch container events
2. Network connectivity — To reach DNS provider APIs
3. Credentials — API tokens for your DNS providers

Docker socket security

The Docker socket provides root-level access to your host. For production deployments, consider using a socket proxy to limit dnsweaver's API access.

Next Steps

Choose the deployment guide that matches your environment, then configure your DNS providers.