> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Domains and TLS

> Multiple domains per node, Cloudflare, certificates and domain selection in Flow and Telegram WEB

Open **Nodes → desired node → Domains and TLS**. One node can have multiple domains: each has its own DNS settings, verification results and certificate information. The first becomes the main one; later the main one can be changed.

## Add a domain

1. Open the domain add wizard and specify a name, such as `node.example.com`.
2. Select manual DNS or Cloudflare. For Cloudflare, use the appropriate integration or optional save token: [setup DNS](https://docs.axottle.com/en/cdn/dns.md).
3. Check A/AAAA. For direct entry, records must be led to IP nodes without CDN proxies.
4. Check the result and keep the binding. Certificate release is run separately; retention alone does not release it.
5. For TLS input, release or check the selected binding certificate.

When you go back, the wizard fields are saved. During a DNS operation, wait for the result. A domain discovered from Remnawave or a certificate, first save it to Axottle: the record you find is not yet equal to the configured binding.

## Use in Flow and Telegram

In the fast entrance constructor and on the tab **Protection** For TLS and SelfSteal, it determines the connection address, the SNI, and the certificate path. After changing the node, select the anchor again, and the server checks its identity when you save and use it.

Older schemes with no explicit choice continue to use the main domain. Before changing it, check such schemes and re-examine the plans of those affected by Flow. The explicitly selected binding allows you to not depend on changing the main domain.

[Telegram WEB](https://docs.axottle.com/en/connection-units/telegram-proxies.md) also selects a domain from node bindings. His Caddy issues its own certificate when installing a proxy; the certificate for a regular Flow TLS input is serviced separately.

> [!WARNING]
>
> Several domains do not exempt occupied ports. Telegram WEB requires TCP 80/443. SelfSteal's shared HTTPS server on the node serves one selected domain: incompatible domains of existing inputs block application. Conventional TLS inputs can use different domains on different ports.

## Verification

Check the DNS and the certificate of the selected binding, then the client address and the SNI in the Flow plan. After applying, check the connection by the client. A successful DNS does not prove that the port is open or the service is running.

## Retraction and removal

To return, restore the previous main domain or select anchors in Flow and apply the plan viewed.

Deletion of the primary or used domain is blocked, including when using a valid Flow, Telegram proxy or SelfSteal.First transfer dependencies and, if necessary, assign a different main domain. Removal of the anchor does not delete the DNS records from the provider and certificate files on the node: they are cleaned separately after verification of use.

The availability of features depends on the version installed; code verification is not a substitute for checking your infrastructure.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.