Frequently asked questions

No. Chorus stores and governs DNS records and domains. It does not answer DNS queries and has no integration that writes records to a DNS provider.

Only published ones, through the public directory, and only their allowlisted fields. Everything else needs sign-in and a role in the record’s organization.

Through Zitadel, the shared Fleetworks identity provider. There is no self-signup: your first sign-in creates a user with access pending until an org:admin grants you a role.

It is a record’s mode in octal. The record owner and the organization’s members may view, edit and delete; everyone else may do nothing. Publishing adds the other-view bit (0o774).

A, CNAME, TXT and SRV.

Compute HMAC-SHA256 of the X-DNS-Timestamp value, a dot and the raw body, keyed with the webhook’s signing secret, and compare it with the X-DNS-Signature header (sha256=<hex>). Deduplicate by X-DNS-Delivery: deliveries are at least once.

Chorus retries with backoff. After five failed attempts the delivery is dead-lettered, and the organization’s registered mobile devices get a push alert.

Not yet. The repo has an Expo mobile app and a Tauri desktop app with release workflows, but no build has been published.

No. The plans page shows sample pricing only; use the contact form to ask about access.