> For the complete documentation index, see [llms.txt](https://synap.ac/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://synap.ac/docs/integrations/custom-domain-cname.md).

# Custom Domain (CNAME)

Set up a custom subdomain for your Synap portal using CNAME records.

Synap hosts your portal at a `synap.ac` address by default. For example:

```
springfield.synap.ac
```

{% hint style="success" %}
Custom subdomains are available on Pro, Business, and Enterprise plans.
{% endhint %}

You can use a custom subdomain on a domain you own. For example, `learning.springfieldelementary.io`.

### Before you begin

Choose a short, memorable subdomain, such as:

* `learn`
* `training`
* `practice`

You must own the parent domain. The subdomain must not already serve another website.

Contact your Synap onboarding manager or support team with your chosen subdomain. We will provide two CNAME records, one at a time.

### 1. Add the portal CNAME record

Add the first CNAME record and its value to your domain's DNS settings.

{% hint style="info" %}
The record name is your chosen subdomain, such as `practice` or `learning`.

Most DNS providers add the parent domain automatically. Others require the full hostname, such as `practice.mywebsite.com`.
{% endhint %}

See your DNS provider's documentation if you need help. These guides cover [GoDaddy](https://www.godaddy.com/en-uk/help/add-a-cname-record-19236) and [123 Reg](https://www.123-reg.co.uk/support/domains/how-do-i-set-up-a-cname-record-on-my-domain-name/).

Tell us when the record is in place. DNS changes can take up to 48 hours to propagate. Verify the record with [DNS Checker](https://dnschecker.org/#CNAME).

### 2. Add the SSL verification CNAME record

After we confirm the portal record, we will provide an SSL verification CNAME record. Its name contains a randomly generated string.

Add the record to your DNS settings using the same process. It authorises Synap to add your subdomain to an SSL certificate. Your portal will then use HTTPS.

Tell us when you have added the record. It can take 24–48 hours to propagate. Verify it with [DNS Checker](https://dnschecker.org/#CNAME).

### 3. Go live

DNS changes often appear within an hour, but full propagation[^1] can take up to 48 hours so we recommend waiting for this before considering your new domain ready for real-life usage.

Once we confirm the final record, we complete setup within 1–3 working days. Tell us if you need the domain live by a specific date.

Your existing `businessname.synap.ac` address remains active unless you ask us to explicitly deactivate it. We update emails and links when your custom domain becomes the primary portal address.

[^1]: This is essentialy, the time it takes for your new domain to be recognised by different ISPs and servers around the world


---

# 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://synap.ac/docs/integrations/custom-domain-cname.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.