Your resolver is welcome.
Technitium, Pi-hole, AdGuard Home and dnsmasq, alongside public DNS APIs and RFC2136.
Automatic DNS for the homelab
A container starts, a VM boots, a service moves. dnsweaver reads the hostnames and keeps the matching records in your DNS providers.
FREE · OPEN SOURCE · YOUR MACHINE
A small bridge between moving parts
Read hostnames from Traefik, Caddy, nginx-proxy or native labels. Connect Kubernetes, Proxmox VE or Incus too. Run the sources you need together.
Send private names to your own resolver and public names to another provider, using the same workload labels.
Discover names from labels, routing configuration and platform APIs.
Use domain rules to select where each record belongs.
Create and update the matching records; remove owned records when workloads go away.
Technitium, Pi-hole, AdGuard Home and dnsmasq, alongside public DNS APIs and RFC2136.
Split-horizon DNS sends internal and external records to different providers from the same labels.
Structured logs, health endpoints and Prometheus metrics. Credentials can come from files instead of environment values.
Your machine. Your tools.
Run dnsweaver as a container or a standalone binary. The getting-started guide covers source discovery, provider credentials and your first records.
Configure the sources and DNS providers before starting reconciliation. Keep management endpoints on a trusted interface; the docs cover ownership, dry runs and upgrades.