Skip to content

Remove a domain & purchase (planned)

A project domain is a domain you connected to Comwit Cloud so the platform can manage its DNS. This page covers two things: how to remove a domain you no longer want Comwit to manage, and a preview of the planned ability to purchase brand-new domains directly through Comwit.

If you are new here, start with Bring your own domain to see how a domain is connected in the first place, and DNS records for managing the records inside it.

Removing a domain stops Comwit from managing its DNS and tears down the Route 53 hosted zone that was created when you connected it. You can do this from the CLI:

Remove a project domain
comwit domains delete --project <projectId> --domain example.com

The equivalent API route:

API
DELETE /v1/projects/{projectId}/domains/{domain}

When you remove a domain, Comwit:

  • Deletes the active Route 53 records in the zone — including any platform-owned records Comwit wrote for an app hostname (for example, records created by connecting an app to your domain).
  • Deletes the Route 53 hosted zone itself.
  • Soft-deletes the project-domain row. The domain is not erased: its audit and operation history stays inspectable, and you can re-add the same domain later if you change your mind.

The plan is to let you search for an available domain, check its price, and order it without leaving Comwit. The designed (but not yet shipped) API routes are:

Planned API routes
GET /v1/domain-availability?domain=example.com
GET /v1/domain-prices?tld=com
POST /v1/projects/{projectId}/domain-orders
GET /v1/projects/{projectId}/domain-orders/{orderId}

How these are intended to work:

  • GET /v1/domain-availability — check whether a specific domain can be registered.
  • GET /v1/domain-prices — look up pricing for a top-level domain (for example, com).
  • POST /v1/projects/{projectId}/domain-orders — place an order to register a domain for a project.
  • GET /v1/projects/{projectId}/domain-orders/{orderId} — check the status of a placed order.

These routes will wrap Route 53 Domains and return an asynchronous domain_order resource rather than pretending registration happens instantly — registrar orders take time to complete, so you will poll the order status route until it settles.