How it works

Records start private inside your organization. You decide, record by record, what anyone else may see. Here is the whole loop.

Step 1
Register a domain
An org:admin creates a domain for the organization. Records can only be created under a domain the organization has registered.
Step 2
Create records
A member with a writer role, or a service account with a PAT, creates a record: a name host under that domain, a record type, content, a TTL and a routing policy.
Step 3
Check them
Ask for lint findings with GET /list?lint=1, or read the Health column in the dashboard. Each finding names its rule and a severity of error or warning.
Step 4
Publish what should be public
The record owner or an org:admin chmods a record to set its other-view bit. Only then does it appear in the public directory, read-only.
Step 5
Hear about changes
An org:admin registers a webhook and chooses its events. Each change creates one delivery per subscribed webhook, signed and retried until it lands or is dead-lettered.
Step 6
Keep content clean
Signed-in users can report a record. An org:admin resolves reports in their organization; platform moderators resolve the rest, including reports about published records.

Keep your organization’s DNS records in one place