> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/administration/customization/custom-domains.md).

# Custom Domains

Use your own domain for customer-facing Couchdrop services.

## Overview

Custom domain settings are configured by the **Owner** from **Admin Panel → Security & Organization → Branding**.

## Dynamic SSL Configuration

Provide a domain that has been configured to point to Couchdrop.

Create a DNS CNAME record that points your domain to the Couchdrop domain shown under **Domain Customization**.

For example:

`files.your_domain.com → your_company.couchdrop.io`

The domain configured in Couchdrop must match your DNS configuration.

## FTPS Certificates

If you use FTPS with a custom domain, you will need to provide your own PEM-format certificate that matches the domain.

Certificates must first be added from **Admin Panel → Administration → Keys**. Once added, the certificate can be selected for the custom domain.

## Additional Custom Domains

If you want Couchdrop whitelabelling to apply to additional custom domains, add them to **Additional Custom Domains**.

Each domain must:

* Be configured in **Dynamic SSL Configuration**
* Match the corresponding CNAME configuration


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.couchdrop.io/administration/customization/custom-domains.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.