> 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/configuring-a-custom-domain.md).

# Connect a custom domain

In this section you will learn how to add a Custom Domain to your application

Connect a subdomain such as `app.example.com` to the intended app.

**Before you start:** verify the published app at its existing address and confirm that you can edit the chosen domain's DNS records.

## Open domain setup

1. Open **More → General**.
2. Find **Custom Domain**.
3. Open its configuration control. For an existing configured entry, use the edit icon.
4. In **Connect a domain**, enter the exact subdomain without `https://`.
5. Select **Continue** and follow the DNS instructions displayed for your app.
6. Review the setup and complete **Add Domain** when the required configuration is ready.

![Connect a domain dialog with a subdomain field, Continue, and Add Domain](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FjRjsZgOpsl2XSIeKVFeu%2Fconnect-domain.png?alt=media)

## Configure DNS using the supplied values

Record the type, host/name, and target/value shown in the setup flow. Enter those values in your DNS provider's controls, accounting for whether that provider expects a full hostname or a subdomain label.

For example, `app.example.com` identifies the intended hostname; it does not specify a universal DNS target. Use the actual target provided for your app and deployment. DNS update timing varies, so check the configured records and status rather than relying on a fixed delay.

## Verify the connection

Return to **More → General → Custom Domain** and inspect its status.

![Custom Domain section showing an existing entry with Domain is configured status and an edit control](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FW2yOOcFEGM4WG7j2Hh5H%2Fdomain-location.png?alt=media)

Open the exact custom address and confirm that the intended app loads. Test sign-in, relevant pages, and a permitted action using an intended account. Review identity-provider callback settings if your authentication flow depends on the app address.

If a check fails, use [Troubleshoot a custom domain](/jet-bridge-deployment/custom-domains/troubleshoot-a-domain.md). For self-hosted deployments, use [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).


---

# 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/configuring-a-custom-domain.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.