Use the type-aware record editor in PD BIND 9 DNS 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 BIND 9 DNS → 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.

Review each saved TTL and keep values for the same DNS record set consistent. 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 BIND 9 DNS zone is not authoritative.

If the change cannot be activated

A successful validation and file write are separate from the running BIND service loading the change. If the result reports an activation or reload failure, preserve the exact redacted message and ask the server administrator to investigate. Check current records before repeating the write; do not assume an error means nothing changed.

Check the website destination

Your hosting team should compare the intended hostname and website destination with the complete saved A/AAAA/CNAME set, selected provider and actual authoritative answer. Review IPv6, aliases and old cached answers separately from the site’s virtual host and HTTPS configuration. Have your BIND administrator inspect validation or activation failures, including whether the file changed before reload failed, before repeating a write.

See the PD BIND 9 DNS WHMCS guide for related tasks, or explore the module.