1. Identify who supplies the public address and whether your plan allows reverse DNS management. Obtain the relevant address or network assignment reference.
2. Choose the intended fully qualified hostname, such as mail.example.com, and configure its forward A or AAAA record to the appropriate public address.
3. List existing reverse DNS resources so you do not create a duplicate request for the same assignment.
4. POST ip and ptr_hostname. Include prefix_length, an eligible server_id or ownership_reference when your assigned reverse zone requires them.
5. Record the returned public resource ID, task state and errors. Verify the resulting reverse answer through the delegated reverse DNS authority.

PATCH the resource ID with both ip and ptr_hostname; this contract requires those values even for an update. Supply the current row version using If-Match when coordinating concurrent administration. On a stale-version conflict, reload the resource and compare changes before trying again.

DELETE removes the permitted reverse DNS entry. First check mail delivery, monitoring and any application that relies on its hostname. Each mutation requires its own idempotency key; repeat the same request with its existing key only when recovering an uncertain transport result.

• Change reverse DNS for an IP address assigned to you
• Delegate reverse DNS only for addresses a customer actually holds
• Check forward-confirmed reverse DNS for a mail server address
• Understand the DNS record types used for websites and business email