DNS backends

The DNS backend is Everlock's authoritative DNS service.

It lets one Everlock instance answer for whole zones, combine hand-written records with records derived from other Everlock services, and keep DNS inside the same admin surface as sites, mail, images, and registries.

What it is for

Use the DNS backend when you want:

• Everlock to be the authoritative source for one or more zones
• service records to follow Everlock-managed sites, mail domains, or registries
• one admin surface for both DNS data and the services that depend on it

How it fits in the system

• frontend-dns serves DNS over UDP and TCP
• backend-dns-dns provides the authoritative record logic
• the admin backends manage zones, records, and address overlays

DNS is global rather than per-instance. You run one DNS backend and manage multiple zones within it.

Typical operator flow

1. enable the DNS backend and frontend
2. create a zone
3. decide how Everlock should determine public addresses
4. add explicit records and let Everlock derive the rest
5. point registrar NS records at the Everlock server

Getting started

• Getting started: standalone DNS zone — your first encounter with the DNS admin commands, bound to 127.0.0.1:5353.

How-tos

Topology and task-specific walkthroughs, also listed in Guides:

• How to host a root domain on a public static IP
• How to host a root domain with primary at home and secondary on a VPS
• How to host a root domain from a NAT line (GoDaddy)
• How to combine DNS, site, and mail in one zone

Pages

• DNS record derivation and address-mode reference
• Getting started: standalone DNS zone
• Mail backend
• Site backend

Read next

• Known issues — including the systemd-resolved port 53 conflict
• Mail backend
• Site backend
• Architecture