> ## 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.

# DNS for CDN

> How to connect Cloudflare AutoDNS and check DNS from the dashboard

## Connect to Cloudflare AutoDNS

1. Open **Settings → Integration**.
2. In the **Cloudflare AutoDNS** card, click Add Zone.
3. Specify name, root domain, Zone ID and API token.
4. Press **Check**.
5. After a successful check, keep the integration.

## Configure the DNS directly in the master

In the status page and subscription page wizards, you can transfer the Cloudflare API token to create an A/AAAA to the specified IP and choose to save the integration separately. The token needs **one Read** and **DNS Edit** for the appropriate zone. The created record works in DNS-only mode.

Without saving, the token is used for this operation and does not replace previously stored details. When you save the integration gets the name of the found zone; for an already connected zone, its record is reused. The success of changing the DNS and the error of saving the integration are displayed separately: first check the actual record, then correct the save.

The HTTP method requires authorization and `settings.manage`. In the node domain wizard, use an existing integration or a temporary token: [Domains and TLS](https://docs.axottle.com/en/nodes/domains.md).

## Enable automatic DNS for node

1. Open the node page → **Domains and TLS**.
2. Specify the domain.
3. Select the automatic DNS mode.
4. Save the configuration and press DNS check.

In the Yandex Cloud automatic scenario, the zone is determined through a connected CDN account, and the operation status is visible in the Flow CDN block.

> [!WARNING]
>
> Integration removal does not delete pre-created records from the DNS provider.

## AutoDNS Readiness

Automatic mode requires proven integration of Cloudflare with the saved details and the area covering the domain. If there are several such integrations, the most specific suitable zone is selected. Having an arbitrary connected account does not mean that it can change this domain.

If you make a mistake, check the integration status, zone and rights of the token, then repeat the check. For existing records, first find out the owner: clearing managed resources should not delete someone else's DNS record.

## Verification and rollback

Check the actual DNS responses and public route after the change. To roll back, restore previously saved records or use a regular cleaning of the created resource, taking into account its owner. Verification: 2026-09-06.


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