Host DNS zones for your organization

The DNS tab holds the zones your organization owns on Coritan's authoritative nameservers. They are the domains you add, such as your storefront's domain, your mail domain or the base domain of your game proxy, and the names your customers claim under a platform domain from your storefront.

• Every member can see the zones and their records. Creating, changing and deleting them needs the owner or admin role.
• You need a domain you control at a registrar, so you can point its nameservers at Coritan.

1. In the dashboard, open the organization, then DNS.
2. Select New zone.
3. Enter the Domain, such as example.com, then select Create zone. The zone opens.
4. The zone starts with NS records at @ that name Coritan's nameservers. At your registrar, set the domain's nameservers to those names.

Coritan signs every new zone with DNSSEC. When DNSSEC reads Signed, the zone page shows the DS record to give your registrar. Until you add it there, resolvers treat the zone as unsigned. Set up DNSSEC explains the DS record.

1. In the DNS tab, select the zone, or Records in its row.
2. Select Add record, or select a record to edit it.
3. Fill in the record:
   • Name: @ for the domain itself, or a label under it, such as www.
   • Type: the record type. DNS record types describes each one.
   • Content: what the record answers with, such as 203.0.113.10 for an A record.
   • TTL: how long resolvers may cache the answer, from 1 minute to 1 day.
   • Priority for MX and SRV records, and Weight and Port for SRV records.
   • Comment: a note for your team.
4. For an A or AAAA record, tick Proxy through Coritan to send its traffic through Coritan's edge for TLS and the web application firewall. The origin address then stays hidden.
5. Select Add record, or Save record when editing.

You cannot change the name or type of an existing record. Delete it and add a new one instead.

To delete a record, select Delete record in its row, type the record type to confirm, then select Delete record in the dialog. Resolvers drop it as their caches expire.

To delete a zone, select Delete zone in its row on the DNS tab, type the domain to confirm, then select Delete zone in the dialog. This deletes every record in the zone, and the domain stops resolving through Coritan.

"Domain already registered"

The domain already has a zone on Coritan, in your organization or somewhere else.

"This domain is reserved by the platform"

Coritan keeps this domain for itself. Choose another.

"Zone limit reached"

Your organization holds as many zones as it may. Delete one you no longer use, or contact support.

"proxied is only valid for A/AAAA records"

Only A and AAAA records can go through the proxy. Untick Proxy through Coritan.

The domain does not resolve

Check that the domain's nameservers at your registrar match the NS records at @. Resolvers pick up a nameserver change only as their caches expire.

• How DNS hosting works
• Import and export a zone file
• Load balancing

Reads take any member's access token; changes take the owner or admin role. The paths below are under /api/v1/orgs/acme/dns.

Create a zone, then add a record to it:

curl -X POST "https://api.coritan.com/api/v1/orgs/acme/dns/zones" \
  -H "Authorization: Bearer $CORITAN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"domain": "example.com"}'

curl -X POST "https://api.coritan.com/api/v1/orgs/acme/dns/zones/{zone_id}/records" \
  -H "Authorization: Bearer $CORITAN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name": "www", "record_type": "A", "content": "203.0.113.10", "ttl": 300}'

A record takes name, record_type, content, ttl (60 to 86400 seconds, 300 by default), priority, weight, port, proxied and comment. record_type is one of A, AAAA, CNAME, MX, TXT, SRV, NS, CAA, PTR, SVCB, HTTPS and DS.

Zones and records:

Load balancing is API only for organization zones. It works as Load balancing describes for websites:

The older /zones/{zone_id}/lb-pools paths take the same requests as /pools.