dnsweaverGet started

Automatic DNS for the homelab

Your services move. Your DNS keeps up.

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

Workloads connect to the right DNSDocker, Proxmox and Kubernetes feed dnsweaver. It reconciles records in internal and public DNS.DockerProxmoxKubernetesInternal DNSPublic DNSYOUR RESOLVERYOUR PROVIDERdnsweaverOne set of hostnames. The right records.
Workload hostnames in. Internal and public records out.
Containers, VMs & clustersInternal + public DNSOne Go binary · amd64 / arm64

A small bridge between moving parts

Let the labels do the typing.

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.

Read the workload.

Discover names from labels, routing configuration and platform APIs.

Match the provider.

Use domain rules to select where each record belongs.

Keep it reconciled.

Create and update the matching records; remove owned records when workloads go away.

Your resolver is welcome.

Technitium, Pi-hole, AdGuard Home and dnsmasq, alongside public DNS APIs and RFC2136.

One name, two views.

Split-horizon DNS sends internal and external records to different providers from the same labels.

See what it's doing.

Structured logs, health endpoints and Prometheus metrics. Credentials can come from files instead of environment values.

TechnitiumCloudflareOVHcloudRFC2136PowerDNSPi-holeAdGuard HomeOPNsensepfSenseUniFidnsmasqWebhook
Rivet the jackdaw has resolved every imaginary price to zero

The pricing department

Every plan resolves to $0.

All of it is free and open source. Rivet has a slightly longer explanation.

Your machine. Your tools.

One fewer thing to update by hand.

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.