# Custom Domains

{% hint style="info" %}
This functionality is limted to Extensive package events
{% endhint %}

{% hint style="warning" %}
**Warning:** we recommend using Cloudflare to use root domains (e.g. `example.com`) with this feature. \
For organisers that do not use Cloudflare, please use subdomains (e.g. `event.example.com`) for your custom domain.
{% endhint %}

A custom domain can be set up either after purchasing a domain yourself or by ordering a custom doman for a fee by contacting your personal Event Consultant.

### Option 1: We handle everything for you

If you’d prefer Let’s Get Digital to manage your custom URL setup, just let your Event Consultant (EC) know your preferred domain.

We’ll take care of the request and connect the approved URL to your virtual event environment. 

#### Costs

To set up a custom domain, we charge a **one-time setup fee of €250** for the configuration and related work.

In addition, there are **annual domain registration costs**. These depend on the domain extension (for example *.com* or *.nl*) and follow the pricing of our domain provider **TransIP**.

#### Registration period

By default, the domain is registered for **2 years in advance** to ensure the domain remains reserved.

If you prefer not to register the domain for two years, we can also **register it for 1 year**. In that case, the domain will be registered for one year and **cancelled immediately after registration**, so it will automatically expire after that year.

### 🌐 Option 2: Setting Up a Custom Domain that you own (Cloudflare)

You can use your own domain (e.g. `event.yourdomain.com`) to host your event environment. This requires adding specific DNS records and confirming domain ownership via Cloudflare.

***

#### Step-by-Step Overview

#### 1. Add the Custom Domain in the Admin Panel

* Go to <kbd>**Settings**</kbd> → <kbd>**General Settings**</kbd> →  <kbd>**Domain**</kbd> in the Admin Panel.
* Enter your domain (e.g. `www.customer.com` or `event.customer.com`).
  * Do **not** include anything after the domain (e.g. no `/page` or path).
* If you are using the same domain for multiple events, enable:

  > `Are multiple environments hosted on this domain?`\
  > This ensures each event is served at a unique path like `/4567-event-name`.

After saving, the domain will be submitted to our Cloudflare integration for processing.

<figure><img src="https://772941315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M5LNCGpK5lyymcFZU4V%2Fuploads%2F3XQJDV5vRKcTlt8PsBoQ%2Fimage.png?alt=media&#x26;token=a7cf0499-70c3-473f-9c32-ede7cd67873b" alt=""><figcaption></figcaption></figure>

#### 2. Inform Your Consultant

Please contact your **Event Consultant** and provide:

* The full domain you entered
* The environment ID (e.g. `4567-event-name`)
* Confirmation that you wish to use a custom domain

Once the domain is registered, you'll receive an email with DNS records that need to be added to your domain’s DNS provider.

***

### 📥 DNS Records to Add

Ask your domain administrator or hosting provider to add the following records.

{% hint style="warning" %}
**Warning:** Please check that your records are showing up after you have updated your DNS records.\
\
Run the `dig` command in your terminal to confirm that your DNS records contain an answer section with the values added to your DNS:
{% endhint %}

#### CNAME Records

These route your domain or subdomains to our platform.

<table><thead><tr><th width="109">Type</th><th width="95">Name</th><th>Content</th><th width="127">Proxy Status</th><th>Purpose</th></tr></thead><tbody><tr><td>CNAME</td><td><code>@</code></td><td><code>live.letsgetdigital.com</code></td><td>DNS Only</td><td>Routes <code>yourdomain.com</code></td></tr><tr><td>CNAME</td><td><code>www</code></td><td><code>live.letsgetdigital.com</code></td><td>DNS Only</td><td>Routes <code>www.yourdomain.com</code></td></tr><tr><td>CNAME</td><td><code>event</code></td><td><code>live.letsgetdigital.com</code></td><td>DNS Only</td><td>Routes <code>event.yourdomain.com</code></td></tr></tbody></table>

{% hint style="info" %}
Most DNS providers use `@` to refer to the root domain.\
Keep proxying turned off (grey cloud) to allow validation.
{% endhint %}

#### TXT Records

These are needed to issue a secure SSL certificate via Cloudflare.

<table><thead><tr><th width="109">Type</th><th>Name</th><th>Value (Example Only — Replace with Actual)</th><th>Purpose</th></tr></thead><tbody><tr><td>TXT</td><td>_acme-challenge</td><td><code>vTeevERC38_SBiBciAZiBQClxvkV71xgjJzBJ5GyAfs</code></td><td>Verifies @ (root domain)</td></tr><tr><td>TXT</td><td>_acme-challenge.www</td><td><code>vTeevERC38_SBiBciAZiBQClxvkV71xgjJzBJ5GyAfs</code></td><td>Verifies www subdomain</td></tr><tr><td>TXT</td><td>_acme-challenge.event</td><td><code>vTeevERC38_SBiBciAZiBQClxvkV71xgjJzBJ5GyAfs</code></td><td>Verifies event subdomain</td></tr></tbody></table>

{% hint style="info" %}
📩 These values will be sent to you after domain submission.\
Please ensure they’re added exactly as shown.
{% endhint %}

***

### When Setup Is Complete

Once the correct DNS records are added and propagated:

* Your domain will be verified.
* An SSL certificate will be issued.
* All event links, emails, and Admin Panel URLs will update to use your custom domain automatically.

We will notify you once the domain is fully active.

***

### Additional Notes

* If your domain is managed through Cloudflare, no business plan is required — we handle that.
* If you’re using a different DNS provider, no problem — you just need the ability to edit DNS records.
* If you're using multiple domains or have specific routing needs (e.g. white-labelling), your Event Consultant can assist further.

### Frequently Asked Questions

<details>

<summary>What is the root domain?</summary>

The root domain is the foundational, top-level registered name of a website, serving as the main entry point of the website.&#x20;

<p align="center"><code>example.com</code></p>

This is the most important part of an address, and it can be built upon by adding subdomains which point to different pages on the website.

<p align="center"><code>event.example.com</code></p>

{% hint style="warning" %}
**Important:** if a customer is not using Cloudflare, they should **not** add a custom domain that points to the root address. We strongly advise using a subdomain instead such as `live.example.com` or `event.example.com`
{% endhint %}

</details>

<details>

<summary>Can I use the root domain for my custom domain if I am not using Cloudflare? </summary>

Generally not. It is possible to do so if the custom hostname is validated for the **[www](http://www).** subdomain, and that the organiser themselves points their root towards it.  However, we strongly recommend making use of a subdomain instead.&#x20;

</details>