go53 manages authoritative DNS through an API
go53 is an authoritative DNS server written in Go. It is built around managing DNS records through an API instead of editing zone files by hand. It currently supports API-managed records, DNSSEC signing, NSEC/NSEC3, key lifecycle work, zone transfers, and change notifications between DNS servers.
It also includes TSIG, catalog zones, and replication across distributed servers. The replication system uses signed events, vector clocks, and Merkle repair to keep servers in sync. A small SvelteKit web admin tool is available for trying it without writing API calls.
A public demo is also available, resets from time to time, and includes a go53.demo. DNSSEC zone with common record types.
Key points
- go53 is an authoritative DNS server written in Go.
- DNS records are managed through an API instead of hand-edited zone files.
- It supports DNSSEC, NSEC/NSEC3, key lifecycle work, zone transfers, and notifications.
- It includes TSIG, catalog zones, and distributed replication.
- A SvelteKit web admin tool and resetting public demo are available for testing.
Quick term guide
- authoritative DNS server
- A server that gives the official DNS answers for a domain.
- zone files
- Files that store DNS settings for a domain.
- notifications
- Messages from an app that remind a user to take action.
- replication
- The process of automatically copying data across multiple machines so that no data is lost if one machine fails.
- API calls
- Each time your code contacts the LLM service to get a response, that counts as an API call and costs money.
- self-hosted
- Run on your own server instead of managed by another company.
- self-host
- To run a website, app, or service on your own server instead of using a hosted provider.
- automation
- A way to make repeated work happen without doing every step by hand.