Getting started

CNX's DNS service is managed entirely through git. There are two repositories your team may have access to. CNX gives you the exact clone URL for each during onboarding — both live at git.cnx.net.kh under a path shaped like customers/example-org/dns/:

zones — the zone configuration you edit. Push a change and open a merge request; validation runs automatically and completes within about 30 seconds. Once a Checker merges it, deployment is automatic too — live within about 120 seconds.
reports — read-only, written by CNX. Present if your subscription includes the compliance evidence package: daily activity logs, DNSSEC key attestation, and a timestamped manifest your team can use as independent audit evidence.

See Identity and access for how to actually authenticate to git.cnx.net.kh — that has to be set up before either repository is useful to you.

The zones repository

git clone git@git.cnx.net.kh:customers/example-org/dns/zones.git
cd zones

See Zones repository format for what's inside — one contacts.yaml plus one directory per zone. contacts.yaml changes go through the same branch → commit → push → merge request flow as any other change in this repository. Managing zone changes covers the actual workflow, including adding your first zone.

The reports repository

Where your subscription includes it, mirror reports to your own infrastructure on a schedule that suits your retention requirements — a nightly pull after 01:00 ICT will have the previous day's report ready before your business day begins:

git clone git@git.cnx.net.kh:customers/example-org/dns/reports.git
# then, e.g. nightly:
git -C reports pull --ff-only

See Reports repository format for what each file contains.

Getting help

For operational issues, contact CNX via the support channel in your service agreement. For billing and subscription changes, contact your CNX account manager.