Use an A, AAAA or CNAME record to publish the intended destination for the website your hosting team or your customer is configuring. PD Cloudflare DNS edits the provider zone directly, so check the exact name and existing records before saving.

Open the right zone

Sign in to the Blesta client area and open My Tools in the client portal, then the DNS manager, then the intended zone’s records. Staff can use PD Modules → Cloudflare DNS → Zones → Records. Client editing requires assignment and permission to change the zone.

Confirm that the domain uses the intended authoritative DNS provider. Creating a record in a zone that is not authoritative does not change the answer visitors receive from the active DNS service.

Choose the record type

Use A for an IPv4 address, AAAA for an IPv6 address, or CNAME for the hostname target your provider requests. The name @ represents the zone’s root in the editor; www is a common separate hostname. Use the values for your actual hosting service, not a copied example address.

Save and check the record

1. Review existing records for the same name, including conflicting CNAME or address records.
2. Choose Add record and select the required type, or Edit the intended existing record.
3. Enter its name and destination, then the appropriate TTL.
4. Review Route through the CDN proxy when available for that record. Decide whether the service should use Cloudflare’s proxy or a direct DNS-only destination.
5. Save and confirm the type, full name, content and proxy state in the list.
6. Check the DNS answer and the website/HTTPS service separately.

A record update is not a website deployment or certificate configuration. A proxied record can return Cloudflare addresses rather than displaying the origin directly; review the intended proxy state when interpreting a lookup.

If the result differs

Check the authoritative nameservers, exact hostname, record conflict, proxy status and cached DNS answers before editing repeatedly. TTL affects cached answers; saving to the provider is not a promise that every resolver changes immediately.

If the form refuses a change, keep the record type/name and redacted error. Your hosting team should check whether a client lock, managed record, package rule or provider permission refused that action. Do not delete unrelated records to make a conflicting name disappear.

Check the saved website record

Your hosting team should compare the complete hostname, type, saved destination, TTL and proxy state with the intended website and authoritative DNS answer. Your DNS and web administrators should separate a refused module write, stale lookup, proxied answer, origin configuration and HTTPS failure. Review any client lock, managed record or allowance before another edit; a valid DNS record does not deploy the website or configure its certificate. Do not remove unrelated records to investigate one hostname.

See the PD Cloudflare DNS Blesta guide for related tasks, or explore the module.