---
title: "Use a custom domain"
description: "Serve a computer on a subdomain you own, such as app.example.com, with two DNS records."
canonical: "https://www.cool.computer/docs/use/custom-domains"
last_updated: "2026-11-22"
---
# Use a custom domain

> Serve a computer on a subdomain you own, such as app.example.com, with two DNS records.

A computer can also answer on a custom domain: a subdomain you own, such as `app.example.com`. It serves exactly what `name.cool.computer` serves, public or private alike, and `name.cool.computer` keeps working.

## Connect a custom domain

```sh
cool domain set bakery app.example.com
```

`cool domain set` prints the two records to create at your DNS provider:

| Type    | Name                              | Value                              |
| ------- | --------------------------------- | ---------------------------------- |
| `TXT`   | `_cool-challenge.app.example.com` | the token `cool domain set` prints |
| `CNAME` | `app.example.com`                 | `fallback--domains.cool.computer`  |

The `TXT` record proves you control the name, and it must resolve within 72 hours. The `CNAME` sends visitors to the computer. The domain is usually live a few minutes after both records resolve, with its certificate issued for you.

Use a subdomain: an apex such as `example.com` and a wildcard such as `*.example.com` can't be connected. Write an internationalized name in its punycode form (`xn--…`).

## Check its state

```sh
cool domain show bakery
```

`cool domain show` prints the hostname, its state and, until it is live, the two records. The states, in order:

| State       | Meaning                                                     |
| ----------- | ----------------------------------------------------------- |
| `challenge` | Waiting for the `TXT` record                                |
| `issuing`   | The name is yours; the certificate is being issued          |
| `serving`   | The domain is set up; the first check through it is running |
| `active`    | Live                                                        |
| `removing`  | Being removed                                               |

When it waits for something, or an `active` domain is not serving right now, `cool domain show` says why.

## Remove it

```sh
cool domain remove bakery
```

The domain stops serving within seconds, and the hostname can be connected again within about a minute. Delete the two DNS records afterwards.

## Limits

- A computer has one domain. Setting another hostname replaces one still waiting for its `TXT` record.
- An account has at most 10 domains, and at most 3 waiting for their `TXT` record.
- Page comments show on `name.cool.computer` only, not on your domain yet. Share the `cool.computer` address when you want comments.
- Only the computer's owner can see or change its domain.

The HTTP API (`PUT`, `GET` and `DELETE` `/api/computers/{id}/domain`) and the [MCP server](/docs/agents/other-mcp-clients#connect-it-yourself) connect and remove domains too.
