Use the type-aware record editor in PD PowerDNS to point a hostname to the destination prepared by your hosting team. DNS points visitors towards a service; it does not configure the site’s virtual host, HTTPS certificate or application.

Choose the appropriate record

Use A for an IPv4 address, AAAA for an IPv6 address and CNAME for a hostname alias. Use only destinations supplied for this website. A CNAME target is a hostname, not a full web URL, and cannot coexist with ordinary records at the same name.

Add or change the intended value

1. Open PowerDNS → Zones, select the zone and review the existing name/type records.
2. Choose Add record, or Edit on the exact existing row.
3. Select A, AAAA or CNAME and enter the intended name and address or target.
4. Review the TTL and save.
5. Read back the entire record set, not just the changed row.

PowerDNS values sharing a name and type share a TTL. Adding another A or AAAA value can leave both destinations answering; use an intentional edit/removal when replacing an old address. Check IPv6 too if only some visitors reach the wrong server.

Verify DNS and the service separately

Compare the domain’s delegated nameservers with the server hosting this zone. Check authoritative answers first, then allow for previous cached answers to expire. Open the actual website and check HTTPS independently.

If the zone is a secondary, make the change at its primary instead. If the record saved but the website is wrong, preserve the hostname, expected destination and redacted result rather than recreating the zone. See the delegation guide when the intended PowerDNS zone is not authoritative.

Check disabled native record members before editing

PowerDNS can retain disabled members in a native record set. The module displays enabled members of recognised types and rebuilds an affected set from enabled members when writing it. Disabled members in that same set can therefore be removed by a module change. If your deployment uses disabled records, have your PowerDNS administrator preserve and review the native set through your authorised server process before editing it here. Module snapshots and BIND exports omit disabled members, so they do not preserve that native state.

Check the website destination

Your hosting team should compare the intended hostname and prepared website destination with the complete current A/AAAA/CNAME set and authoritative answers. Values sharing a name and type use one TTL, and changing a row can affect that set’s shared TTL. Check old destinations, IPv6 and cached answers separately from the site’s virtual host and HTTPS configuration. After an API refusal or timeout, read current records before repeating a write.

See the PD PowerDNS Blesta guide for related tasks, or explore PD PowerDNS.