Check the active WHMCS service's dedicated or assigned IP data. For an explicitly delegated exclusive address, use the supported client policy and record the reason. A customer can point an A or AAAA record at almost any address; that forward record alone does not establish permission to change its PTR.

If the upstream infrastructure provider retains reverse DNS, use that provider's approved workflow. Adding a reverse-looking record to the customer's ordinary forward zone does not update the IP's real reverse DNS.

1. Connect the backend that holds the reverse zone or provides the authorised reverse-DNS operation.
2. Configure the package's reverse-DNS capability and management mode.
3. Review IP policy and any client-specific exclusive-address evidence. Avoid broad assignments that include shared hosting addresses.
4. Decide whether customer PTR requests apply directly or require administrator approval.
5. Test with an address genuinely assigned to a controlled service.

Open Reverse DNS, select the eligible address and enter the intended fully qualified hostname. Prefer a hostname controlled by the customer and, for mail use, make its forward A or AAAA record return the same address.

Submit the request, review any approval and follow the provider result. Query the actual reverse record after completion and verify the corresponding forward record. Reverse DNS is one input to mail identity and reputation; it does not guarantee inbox placement.

When an IP leaves a customer service, review existing PTR records and the current entitlement. Do not let a stale service mapping grant continued control after reassignment. Withdraw or replace the PTR through the backend that is actually authoritative.

If a request is refused, identify whether the cause is missing IP ownership, no reverse-zone authority, package policy or provider support. Granting DNS record-editing permission does not solve a reverse-ownership failure.

Keep the address, hostname, service and approval evidence together. This is particularly useful when several services share a provider account but only one customer holds a specific address.

• Change reverse DNS for an IP address assigned to you
• Review customer DNSSEC and reverse DNS requests
• Set DNS package limits and customer permissions without blocking the wrong service
• Add a DNS provider connection and prove that it can manage zones