> For the complete documentation index, see [llms.txt](https://manual.personr.co/api-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.personr.co/api-documentation/domain-names/linking-your-domain.md).
# Linking your domain
Linking your domain to the platform is easy, and only takes a few minutes.
To get started, head into the **Dev Space** tab within your dashboard, and select **Domains**. You'll need to activate the Custom Domains addon if you haven't already.
Once you have entered your domain or subdomain, you will need to enter the displayed records within your domain's DNS settings. This tells the internet to point your domain to our content delivery network. Sometimes, you may be required to verify you own the domain name by adding additional records.
Let's say we wanted to link **onboard.personr.co**, your DNS record should look something like the below.
When adding your DNS records, make sure to use the IP address we've provided via the platform.
{% hint style="info" %}
If you use CloudFlare or similar for DNS or domain management, make sure to turn off traffic proxying.
{% endhint %}
Once you've entered the required records in your domain's DNS settings, select **Check Records**. Depending on your provider, propagation may take a few hours. Similarly, it may take a few hours for our system to generate an SSL certificate - though this usually only takes a few minutes.
That's it. Once linked, you can use your newly-linked domain to...
* Access the dashboard;
* Provide branded verification links to clients; and
* Create static verification [Pages](/api-documentation/pages/overview.md) with your domain.
{% hint style="info" %}
If you generate verification links via API, you can replace **enterprise.personr.co** with your linked domain.
{% endhint %}
---
# 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://manual.personr.co/api-documentation/domain-names/linking-your-domain.md?ask=&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.
