Skip to content
Comwit Cloud

Bring a domain you own

A project domain is a domain you already own (like example.com) that you hand to Comwit Cloud so it can manage the domain’s DNS for you. Comwit creates a dedicated DNS zone for the domain, you point your registrar at it, and from then on Comwit is the source of truth for the domain’s records.

This page walks through the delegated DNS flow end to end: onboard the domain, set the nameservers at your registrar, and confirm delegation so record management unlocks.

Step 1 — Onboard the domain

Section titled “Step 1 — Onboard the domain”

Start by telling Comwit about a domain you already own. The CLI:

Onboard a domain with delegated DNS
comwit domains add --project <projectId> --domain example.com

The equivalent API call posts the domain together with the DNS mode:

POST /v1/projects/{projectId}/domains
POST /v1/projects/{projectId}/domains
{ "domain": "example.com", "dns_mode": "route53_delegated" }

Comwit creates the hosted zone and responds with the zone’s id, a starting status of pending_delegation, and the nameservers you need to set at your registrar:

Response
{ "domain": {
    "domain": "example.com",
    "dns_mode": "route53_delegated",
    "status": "pending_delegation",
    "hosted_zone_id": "Z0123456789ABCDEFGHIJ",
    "nameservers": ["ns-1.awsdns-00.com", "ns-2.awsdns-00.net"]
} }

The status pending_delegation means the zone exists but your domain is not yet pointing at it, so record management stays locked until you confirm delegation (Step 3).

Step 2 — Set the nameservers at your registrar

Section titled “Step 2 — Set the nameservers at your registrar”

Copy the nameservers values from the response and update your domain’s NS records at your registrar to exactly those values. This is the step that delegates the domain to Comwit.

Where to do this depends on your registrar (look for “Nameservers”, “DNS”, or “Domain settings”). Replace any existing nameservers with the ones Comwit returned.

Step 3 — Confirm delegation

Section titled “Step 3 — Confirm delegation”

Once you have set the nameservers, ask Comwit to verify that the domain is actually delegated to its zone:

Check delegation
comwit domains check --project <projectId> --domain example.com

The equivalent API call:

POST /v1/projects/{projectId}/domains/{domain}/delegation-check
POST /v1/projects/{projectId}/domains/{domain}/delegation-check

Comwit resolves the domain’s authoritative nameservers (the ones the internet actually sees) and compares them to the hosted zone’s nameservers:

  • They match → the domain moves to status managed and DNS record mutations unlock. You can now create, update, and delete records — see DNS records.
  • They do not match yet → the domain stays pending_delegation. This is normal right after you change nameservers; just wait for propagation and run the check again.

If a managed domain stops delegating

Section titled “If a managed domain stops delegating”

Delegation is checked over time, not just once. If a domain that was already managed later stops delegating to the Comwit zone (for example someone changes the nameservers back at the registrar), Comwit moves it back to pending_delegation:

  • Create and update of records is locked again.
  • Deletes still work, so you are never trapped with records you cannot remove.

Re-point the nameservers and run comwit domains check again to return the domain to managed.

What’s next

Section titled “What’s next”