Create these records once your server is running. Replace example.com with your domain.

No domain yet? You need none of this. Install without one and the workspace answers at onecamp.<your-ip>.sslip.io, which already points at your server. Come back here when you move to your own domain.

make install prints this same list with your own domain filled in. If the two ever disagree, trust the installer: it reads your actual configuration.

Point these at your server

Record	Type	Notes
`onecamp-backend`	A	The API
`onecamp-emqx`	A	Realtime messaging
`onecamp-minio`	A	File storage
`onecamp-collab`	A	Live editing in documents
`onecamp-livekit`	A	Video calls and meetings
`onecamp-turn`	A	Call connectivity. DNS only — never proxy this one

If you use Cloudflare, onecamp-turn must be grey-clouded (DNS only). Media travels over UDP and a proxy cannot carry it, so an orange cloud here does not show an error: calls just never connect for people on restrictive networks.

The address your team opens

Record	Type	Points at
`onecamp`	A	Your server. `make install` serves the web app from it

If you host the web app somewhere else instead (installed with WEB=0, see step 4 of the install guide), point onecamp at that deployment, as a CNAME or an A record, and not at this server.

Do not create records for the admin consoles

Postgres, Redis, Dgraph and OpenSearch are not published to the internet, and neither are the EMQX, MinIO and OpenSearch consoles. A record pointing at them either resolves to something that refuses to answer, or exposes a datastore that was never meant to be reachable. Reach the consoles with make console-tunnel instead.

The Traefik dashboard is behind basic auth and needs no record unless you deliberately want it published.