Public hosting: DNS vhosts and ACME
This page covers reaching one or more image instances from the public internet: how a DNS hostname routes to an instance, and how Everlock issues and renews a TLS certificate for it automatically. It
Documentation
Tag: dns
Public hosting: DNS vhosts and ACME
This page covers reaching an OCI registry from the public internet: how a DNS hostname routes to a registry instance, and how Everlock issues and renews its TLS certificate automatically. It builds on
DNS record derivation and address-mode reference
DNS is global, not multi-instance. Its state is split across: - `everlock-system/config/dns.toml` - `everlock-dns/<zone>.toml` The backend combines:
How to use a third-party secondary (e.g. Hetzner)
This walkthrough points a managed DNS provider's secondary service at your Everlock as the **hidden primary**. You keep editing the zone on Everlock; the provider's nameservers pull it over AXFR and a
How to host a root domain from a NAT line (GoDaddy)
This walkthrough hosts a root domain like `jens.dev` directly from Everlock running at home behind a Fritzbox-style NAT line, with the domain registered at GoDaddy. The home line has a regular dynamic
How to host a root domain with primary at home and secondary on a VPS
This walkthrough sets up two Everlock instances to serve one root domain: - **Everlock A** runs at home behind your Fritzbox on a dynamic public IP. You edit the zone here. - **Everlock B** runs on
How to host a root domain on a public static IP
This walkthrough hosts a root domain like `jens.dev` on a single Everlock instance that has a public static IP — a typical VPS, dedicated server, or paid static line. No NAT, no IP changes, no glue ga
DNS address modes and public-IP discovery
`backend-dns-dns` now picks the address used in synthesised `A` / `AAAA` records (vhost records, `mail.<zone>`, and the `ns1` / `ns2` glue) at runtime, based on an `address_mode` key in `dns.toml`. Th
Getting started: standalone DNS zone
This walkthrough starts Everlock as a local authoritative DNS server, creates one zone, adds a few explicit records, and verifies the answers with `dig`. This is the simplest DNS-first setup: - no HTT
How to combine DNS, site, and mail in one zone
This walkthrough starts Everlock with DNS, site hosting, and inbound mail, then shows how one DNS zone can derive records automatically from: - a site vhost - a mail domain At the end, `jens.dev` is a
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