# Bindings

By default when you create a custom web and then publish your project the Toolkit creates an initial `<tenantname>.webdev.comunity.me` binding for your application.&#x20;

A binding is a domain for your custom website. The ComUnity Developer Toolkit can be configured to point to several bindings for a single custom website.

View [Domain Name System](https://en.wikipedia.org/wiki/Domain_Name_System) to learn more about DNS registration and configuration.

{% hint style="info" %}
ComUnity Platform also serves as a domain registrar, contact sales for more information on how to purchase and manage your domain.

{% endhint %}

To add a custom binding, follow these steps:

1. Open your project in the Toolkit and navigate to Custom Website then select the **Bindings** tab.<br>

   <figure><img src="https://content.gitbook.com/content/d5MjtWYbfFg1tqxrssP5/blobs/Xgl9ADkWym30Gj8NyrY0/image.png" alt=""><figcaption></figcaption></figure>
2. Locate the **Add New Binding**  button and click on it to add a new class.
3. A modal window titled **Add Binding** will appear on your screen.\
   ![](https://content.gitbook.com/content/d5MjtWYbfFg1tqxrssP5/blobs/yEmaCRAOpPMVQAkkAMSl/image.png)
4. In the modal window, provide a add a unique binding for your application in the designated **Binding Name** box.
5. Finally, click **Add**.

After successfully adding a binding contact the ComUnity Toolkit's technical team for further assistance in enabling your binding.


---

# Agent Instructions: 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:

```
GET https://comunity.gitbook.io/learning.comunityplatform/toolkit-guides/custom-website/bindings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.