Confirm an authorised replacement IP is configured and available on the server. Record current DNS values, proxies, allowlists, TLS coverage and application callbacks. Lower relevant DNS TTLs in advance when you control them.

1. Open Change Site’s IP Address and select the exact account. Verify its current IP and associated domains.
2. Choose the approved available destination IP and complete the supported change. Read any warnings from the operation.
3. Inspect local DNS records and separately update records hosted at an external authoritative provider. Do not assume WHM can update a Cloudflare zone or registrar DNS for you.
4. Adjust third-party allowlists or integrations that explicitly use the old address. Check mail-related implications with the administrator before changing sending-IP expectations.
5. Test the website and other affected services at the new address, then monitor during DNS-cache expiry. Retain a deliberate rollback plan while both addresses are still usable.

On a computer with curl, replace the example hostname and documentation IP below with the actual website hostname and approved new address. This sends a header request to that address while keeping the hostname in the HTTPS request.

curl --resolve example.com:443:203.0.113.25 --head https://example.com/

The override applies only to this curl invocation; it does not update public DNS. Review the status and any redirect destination, and test each additional hostname with its own matching override. A HEAD request checks the response headers, so also verify actual pages, forms and business functions through the planned preview method.

Keep certificate verification enabled. A certificate error or an intentionally restricted origin needs investigation through the service’s approved test method, not an automatic --insecure bypass. After cutover, repeat the normal hostname test without the override to verify public routing.

Authoritative DNS and the server’s virtual-host configuration should agree on the new destination. Test with the intended hostname so certificate and virtual-host behaviour are checked correctly.

If some visitors still reach the old IP, compare resolver cache and TTL behaviour. If the new IP serves a default page, inspect account binding and hostname matching. Changing a package does not automatically perform this IP move.

No. Sending reputation, reverse DNS, authentication and recipient policies need separate review. Do not treat an address change as a substitute for correcting abusive sending.

• Changing an account’s primary domain in WHM
• Planning DNS and mail cutover after a WHM transfer
• Changing the hosting origin behind an existing Cloudflare proxy
• Transferring a cPanel account to a different reseller owner

• cPanel: Change Site IP Address
• cPanel: Upgrade Downgrade An Account

• curl: resolve a hostname to a specific address for one request