Use PD DNS Manager to add an A, AAAA or CNAME record at the DNS provider serving your domain. This changes a DNS destination; it does not install a website, configure its virtual host or issue its HTTPS certificate.

Before a change, confirm the provider connection and the actual zone it resolves. With Route 53, name-based operations resolve the first matching hosted-zone name; selecting a familiar domain is not sufficient when AWS holds multiple zones with that name. Have your AWS administrator compare the hosted-zone ID, records and assigned nameservers before proceeding. With Google Cloud DNS, the current connection derives the managed-zone name from the domain. An existing zone with a different native name can appear in a list yet fail to open correctly; establish that mapping with your Google Cloud administrator instead of creating a duplicate zone.

For a PowerDNS backend, module reads and zone-file snapshots omit disabled native record values. Editing an affected record set can rebuild it from the enabled values. If your hosting team uses disabled records, preserve and review the native record set with your DNS administrator before module changes; use your established native management process where those values must be retained. A module export is not a complete backup of those disabled values or other provider settings.

Choose the authoritative zone

Open DNS → Zones, find the domain and choose Manage records. Customers can use My Tools in the client portal, then the DNS manager. Check that the registrar delegates the domain to this provider’s nameservers before expecting public answers to change.

Keep the web host’s requested hostname and destination ready. Use A for an IPv4 address, AAAA for IPv6, or CNAME for another hostname. A CNAME target is not a full web address with a protocol or page path.

Save the intended record

1. Find the existing name/type before adding another record.
2. Choose the record type in the editor.
3. Enter the Name, TTL and address or Target shown for that type.
4. For an existing record, click Edit and review the previous destination before replacing it.
5. Click Save record, then reload the zone and check the saved value.

Do not add a CNAME over existing address records at the same name. Keep an intentional multi-address set rather than deleting working entries indiscriminately. The editor offers types and optional controls according to the selected backend’s capabilities.

Check proxy and visitor results

A Cloudflare-backed zone can offer a proxy toggle. Its choice affects how visitors reach the origin; DNS on another backend does not acquire a CDN proxy simply because the module manages it.

After saving, check the authoritative answer separately from a cached resolver answer, then test the intended website and HTTPS hostname. Clearing a website cache is not a way to expire DNS caches. If the DNS is correct but the site is wrong, review the web hosting and certificate configuration with the web host.

A refused save can concern a zone lock, content policy, quota or a record managed by forwarding. Resolve that cause through its owning feature. Take a zone snapshot before a larger group of changes.

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