DNS Record Management

March 30, 2026 15 views

DNS Record Management

CloudWeb integrates DNS management directly with Cloudflare, allowing you to create and manage DNS records directly from the user panel. DNS settings can be found in the DNS section.

Supported record types

  • A – maps a domain to an IPv4 address
  • AAAA – maps a domain to an IPv6 address
  • CNAME – alias for another domain
  • MX – mail server (requires priority)
  • TXT – text record (SPF, verification, etc.)
  • NS – nameserver record
  • SRV – service record (requires priority, weight, and port)
  • CAA – Certification Authority Authorization
  • SPF – Sender Policy Framework
  • DKIM – DomainKeys Identified Mail
  • ANAME – alias record for root domain
  • NAPTR – Naming Authority Pointer

Creating DNS records

  1. Select the record type
  2. Enter the name (@ for root domain, or a subdomain like blog)
  3. Enter the record content (IP address, target domain, etc.)
  4. Set the TTL (Time to Live) – from 1 minute to 1 day
  5. For MX and SRV records, enter the priority

Cloudflare proxy

A, AAAA, and CNAME records can be routed through the Cloudflare proxy (orange cloud). When proxy is active:

  • TTL is set automatically
  • Traffic goes through Cloudflare CDN with DDoS protection
  • The actual server IP address is hidden

Automatic email DNS setup

The Mail DNS Setup button automatically creates all necessary records for email service:

  • MX record – directs emails to the CloudWeb mail server
  • SPF record – authorizes the server to send emails on behalf of your domain
  • DMARC record – email authentication policy
  • DKIM record – digital email signature

The process automatically creates the domain in the Poste.io mail server, generates DKIM keys, and provisions all records to Cloudflare.

Provisioning status

Records are first saved to the database and then asynchronously provisioned to Cloudflare. Each record's status can be:

  • Pending – waiting for provisioning
  • Provisioned – successfully deployed to Cloudflare
  • Failed – provisioning failed

Limitations

  • SOA and NS records – system-managed, cannot be edited
  • Locked records – set by admin, cannot be modified
  • Subdomain hostings – DNS is managed through the parent/master domain

Was this article helpful?

Your feedback helps us improve our documentation

Still need help?

If this article didn't answer your question, our support team is here to help.

Contact Support