> For the complete documentation index, see [llms.txt](https://docs.codeeqr.com/product-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codeeqr.com/product-docs/dashboard/custom-domains/how-to-connect-your-own-custom-domain.md).

# How to connect your own custom domain

{% hint style="info" %}

* A paid plan is required to connect custom domains.
* Ensure that the custom domain you wish to add is not already in use. To use the domain of your main brand, consider using a subdomain (e.g. 'qr.domain.com').
* Do not use the same custom domain for your custom index page in the submission form.
* Some hosting providers may not allow both A & CNAME records, in which case you can use just the CNAME record."
  {% endhint %}

1. Go to the '[<mark style="color:blue;">Custom Domains</mark>](https://app.codeeqr.com/domains)' tab (or log in first).
2. Click on the "+ Connect Custom Domain" button.
3. Fill in the required fields. Many of our customers use a subdomain (e.g. 'qr.domain.com') to keep using their main domain.
4. The 'Custom Index URL' is the page where your customers will be directed if the custom slug is empty. You can also leave this field blank to show the CodeeQR homepage.
5. The 'Custom 404 URL' is the page where your customers will be directed if the dynamic link is not working. You can also leave this field blank to show the CodeeQR 404 page.
6. Once you have completed the fields, click the "Create" button to save your settings.
7. In order to complete the setup process, you will need to add DNS records to your hosting provider. Use an A record pointing to **143.198.171.114** and a CNAME record pointing to **app.codeeqr.com**.
8. The CodeeQR team will be notified of your submission and will manually connect your custom domain. In some cases, additional verification may be required and we will email you about this.
9. Check the 'Custom Domains' tab to see the status of your custom domain. When the status is 'active', your custom domain is ready to be connected and used in the 'Dynamic Links' tab.
10. Please note that this process may take up to 48 hours to fully sync and become active.

## Example subdomain

If you are using a subdomain as your custom domain, such as 'qr.domain.com', your DNS records should be similar to the following:

| Type  | Host | Value           | TTL       |
| ----- | ---- | --------------- | --------- |
| A     | qr   | 143.198.171.114 | Automatic |
| CNAME | qr   | app.codeeqr.com | Automatic |

*"Please note that it is also possible to use just the CNAME record. Some hosting providers may not allow both A and CNAME records."*

## Example main domain

If you are using your main domain as your custom domain, such as 'domain.com', your DNS records should be similar to the following:

| Type  | Host | Value           | TTL       |
| ----- | ---- | --------------- | --------- |
| A     | @    | 143.198.171.114 | Automatic |
| CNAME | @    | app.codeeqr.com | Automatic |

*"Note that you can also just use the CNAME record some hosting providers won't allow both records."*

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.codeeqr.com/product-docs/dashboard/custom-domains/how-to-connect-your-own-custom-domain.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.