WHM API 1 / DNS

WHM API 1 update_reverse_dns_cache

Find the endpoint, CLI syntax and practical purpose of this cPanel command, with a direct link to the official documentation.

What this command does

The cPanel documentation summary for this operation is: Update reverse DNS cache.

In Hostilla.pl this page helps identify the exact API operation before using automation, reseller integrations or a support request.

Command details

API
WHM API 1 11.136.0.25
Category
DNS
Method and path
GET /update_reverse_dns_cache
Operation ID
update_reverse_dns_cache
CLI example
whmapi1 update_reverse_dns_cache

Open official cPanel documentation

Practical request workflow

WHM API 1 update_reverse_dns_cache should be run only after the target account and expected result are known. Start with a read-only lookup when one is available, then make the smallest required change and verify the resource again.

  1. Confirm ownership of the domain and identify the authoritative DNS zone or redirect source.
  2. Read the current record or redirect set before making a change.
  3. Validate names, record types, targets and TTL values supplied to update_reverse_dns_cache.
  4. Query the authoritative service again and test from a caching resolver or browser.

CLI request example

whmapi1 update_reverse_dns_cache

How to read the response

For DNS and redirect operations, compare the returned record identifiers and values with an authoritative lookup. Propagation or browser cache can delay what users see even after the API accepted the change.

Record the request time, account and domain together with the returned status. A successful transport response does not by itself prove that the requested resource was created, changed or deleted exactly as intended.

Questions before automation

What permission does WHM API 1 update_reverse_dns_cache require?

This WHM API operation requires authorized reseller or administrator privileges and an exact target account.

What should I check before running update_reverse_dns_cache?

Confirm ownership of the domain and identify the authoritative DNS zone or redirect source. Read the current record or redirect set before making a change.

How do I confirm that update_reverse_dns_cache worked?

For DNS and redirect operations, compare the returned record identifiers and values with an authoritative lookup. Propagation or browser cache can delay what users see even after the API accepted the change.

Hostilla.pl usage notes

WHM API commands can affect server or reseller-level resources. They should be used only by authorized administrators or reseller integrations.

Need this operation for your hosting account? Contact Hostilla.pl support with the account name, domain and expected result. We will help select a safe API path.

Related practical guides

Related API navigation