baginskistudio/devns repository overview

⁠DevNS Docker

Official Docker deployment for DevNS (Development Name Server).

DevNS is a lightweight, self-hosted DNS server written in Rust, designed for development environments, internal infrastructure, homelabs, and private networks requiring reliable and configurable DNS services.

This repository provides a ready-to-use Docker deployment, including container orchestration, example configuration, and deployment defaults intended to simplify installation, operation, and maintenance. eduardobaginskicosta/devns⁠.

⁠Features

• Lightweight DNS server implementation.
• Support for custom DNS zones.
• Recursive zone file discovery.
• IPv4 (A) and IPv6 (AAAA) records.
• Name Server (NS) records.
• Mail Exchange (MX) records.
• Configurable upstream DNS forwarding.
• DNS-based domain blocking.
• Persistent configuration storage.

⁠Deployment Model

The container image is designed to operate as a self-contained DNS service while keeping configuration and DNS data external to the container lifecycle. Runtime behavior is controlled through environment variables, while DNS records and zone definitions are managed through mounted configuration files.

This approach allows infrastructure configuration, DNS data, and application updates to remain independent, simplifying upgrades and operational management.

⁠Configuration

DevNS supports configuration through environment variables exposed by the container runtime.

DNS zones are stored separately within the configuration directory and are discovered automatically during startup.

⁠Container Design

The official image is built as a minimal runtime environment focused on portability, predictable behavior, and operational simplicity.

Key characteristics include:

• Minimal container footprint.
• Stateless image design.
• Externalized configuration.
• Persistent DNS data.
• Versioned image releases.
• Production-oriented deployment defaults.

The image is intended to integrate cleanly into existing infrastructure and container orchestration environments without requiring additional dependencies inside the container.

⁠Updates and Versioning

Container images are published alongside project releases and follow the same versioning strategy as the main DevNS project.

Deployments may track either:

• Specific release versions for predictable upgrades.
• The latest tag for automatic adoption of the most recent stable release.

Configuration files and DNS data remain independent from the container image and are preserved across updates.

⁠Project Resources

Source code, documentation, release notes, issue tracking, and development resources are maintained in the main DevNS repository: eduardobaginskicosta⁠.