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

# Custom domains

Give the published app an address on a domain you control.

## Before you start

Have access to your DNS configuration, identify the app and environment, and choose the subdomain you want to use. Verify that the published app works at its existing address first.

* [Connect a custom domain](/jet-bridge-deployment/custom-domains/configuring-a-custom-domain.md) for the current app setup flow.
* [Troubleshoot a custom domain](/jet-bridge-deployment/custom-domains/troubleshoot-a-domain.md) for DNS, connection, or login failures.
* [On-Premise custom domain configuration](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/.env-configuration-local-host/custom-domain-configuration-on-premise.md) for self-hosted deployments.

## Verify the whole user journey

A configured domain is only one part of the release. Test loading, sign-in, a permitted data action, and a restricted action at the new address.

Use the values supplied by the current setup flow for your app. Do not reuse a DNS target or callback URL from a different deployment.


---

# 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.jetadmin.io/jet-bridge-deployment/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.