Skip to content
Coritan Docs

Add a domain you already own

Host the DNS for a domain registered elsewhere on Coritan, then point the domain's nameservers here.

View as Markdown

In the dashboard

Add a domain registered with another registrar when you want Coritan to host its DNS. Coritan creates a DNS zone for the domain, and the registration stays where it is. Once you set Coritan's nameservers at your registrar, the zone's records answer for the domain. To move the registration to Coritan as well, transfer the domain.

  • Make sure you can change the domain's nameservers at its current registrar.
  • Write down the records the domain uses today, such as its website address, its mail servers and any verification TXT records. Add them to the new zone before you change the nameservers, or the domain stops resolving until you do. If your current DNS provider can export a BIND zone file, you can import it.
  1. In the dashboard, go to Websites and select Add existing domain….
  2. Enter the Domain name, such as example.com, and select Add domain.
  3. The dialog now lists the nameservers to set at your registrar. Copy them.
  4. Select Open DNS to go to the zone's DNS tab, and add the records the domain needs. Add, edit and delete DNS records explains the form.
  5. At your registrar, replace the domain's nameservers with Coritan's.

Note

The dialog lists two nameservers. The zone's NS records, at @ on its DNS tab, list every Coritan nameserver (ns1.coritan.com to ns8.coritan.com), and you can give your registrar the full set.

The domain appears in the Websites list as DNS hosted here. Coritan signs the new zone with DNSSEC from the start; Set up DNSSEC explains the step left at your registrar.

The switch happens once your registrar publishes the new nameservers, and resolvers keep the old ones until their cached answers expire. Check the delegation from a terminal:

Shell
dig NS example.com +short

When the answer lists Coritan's nameservers, the zone is live. The domain's Overview tab then starts to count queries (View DNS query statistics).

Enter a domain, such as example.com.
The dashboard could not read the name as a domain. Enter the bare domain, without https:// or a path.
Domain already registered
A DNS zone for this domain already exists on Coritan. If it is yours, it is in your Websites list. If another account holds it, contact support.
This domain is reserved by the platform
The domain is one of Coritan's own, or a name under one. For a name under coritan.gg, claim a free name instead.
Conflicts with the existing zone example.com, which belongs to another account
Another account hosts a zone that contains your domain, or a zone inside it. Coritan refuses zones that overlap across accounts.
Zone limit reached (100)
The account hosts as many zones as it may. Delete a zone you no longer use.

Create the zone with an access token (Authentication). The body takes one field, domain:

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

The answer is 201 with the zone. Keep its id: every other DNS call names the zone by it.

JSON
{
  "id": 42,
  "domain": "example.com",
  "status": "active",
  "dnssec_enabled": true,
  "serial": 2026092501,
  "soa_email": "hostmaster",
  "record_count": 8
}

The zone starts with its NS records, one for each Coritan nameserver. List your zones, sorted by domain, with GET /api/v1/dns/zones. It returns 25 zones a page by default; per_page takes up to 100, and page counts from 1.

Shell
curl "https://api.coritan.com/api/v1/dns/zones?per_page=100" \
  -H "Authorization: Bearer $CORITAN_TOKEN"

API operations on this page

MethodPathWhat it does
POST/api/v1/dns/zonesCreate zone
GET/api/v1/dns/zonesList zones