IP binding is the feature which allows you to bind any Plesk license to a certain server IP address.
How does IP binding works?
There are two possible behaviors of “IP binding” feature:
- “Lookup only”
This behavior is the default one and is useful for cases when you need to reinstall Plesk on the same server. For example, you have a Plesk server with a production license which is bound to the server IP address. After you reinstall Plesk, you get clean Plesk instance without any data and license file. Plesk will connect to Key Administrator and get the license file with the server IP address.
- "Lookup and Restrict"
In addition to “reinstall” scenario, this behavior also includes “restrict” scenario. It allows restricting a Plesk license for use only on one server.
When your Plesk license is bound to some IP address and has “Lookup and Restrict” behavior selected, it can be used only on that server. If someone tries to copy the license file and install it on a different server, this new instance of Plesk will fail to update license.
This behavior can be helpful for partners who want to restrict usage of their Plesk licenses to certain IP addresses and avoid piracy.
How can I manage IP binding?
IMPORTANT: IP binding management is available only for Plesk partners having access to Key Administrator and/or Key Administrator Partner Central . If you are a Plesk partner and need to change IP binding behavior, log in to your account in KA/KAPC.
IP binding behavior can be set at two levels:
All existing clients have “Lookup only” selected.
- All newly created clients have “Lookup only” selected by default.
IP binding behavior can be set to “Lookup and Restrict” for the required client.
All existing keys have “Lookup only” .
- When a new key is created, it inherits the behavior specified for its client.
- IMPORTANT : changing behavior for a client does not change the behavior for already existing keys under this client. “Inheritance” works only during key creation. So if the behavior is set “Lookup and Restrict” for an existing client, it should be also switched to “Lookup and Restrict” explicitly for all previously created keys.
NOTE: partners using Partner API 3.0 can switch licenses between “Lookup only” and “Lookup and Restrict” behaviors using “restrictIPBinding” field. For more details, see https://central.plesk.com/docs/partner-api/3.0/63414.htm#
IP binding does not work with IPv6. Key Administrator does not have IPv6 address, therefore no IPv6-to-IPv6 routing is possible.
If you are a partner and use some load-balancing solution in front of Plesk server that causes use of dynamic public IP address, then:
- You should either take care of directing the outgoing traffic to ka.plesk.com via a permanent public static IP address
- Or should not use IP binding
If are a partner and have multiple public IP addresses on their server, and any of these IP addresses may be used as an address for outgoing connections, then:
- You should either take care of directing their outgoing traffic to ka.plesk.com via a permanent public static IP address
- Or should not use IP binding