2.2.1. Dedicated IP for hosting

By default, all sites of the hosting account run on a shared IP. In order for a site or several sites to work on a separate IP, you can order a dedicated IP.

Dedicated IP available only in Ukraine. If the hosting account is hosted in another country, then to order a dedicated IP you will need it change.

Important points:

  • The dedicated IP is linked to the hosting account and ordered for a period equal to the remaining validity period of this hosting account. Further, the dedicated IP will be included in check to renew your hosting account. If the need for a dedicated IP disappears, its renewal can be disable.
  • For one hosting account, you can order any number of dedicated IPs.
  • Only dedicated IPv4 addresses are available. IPv6 addresses are not provided.
  • Dedicated IPs are allocated by the system automatically. It is impossible to look through the list of available addresses before ordering and choose the one you want.
  • All dedicated IPs ordered for the hosting account will be from the same subnet. You cannot get a dedicated IP from another subnet.
  • The dedicated IP will be for the country where the hosting account is located. It is impossible to migrate to another country while maintaining the dedicated IP — you will need to refuse it and order a new one after migration.
  • Dedicated IPs cannot be transferred between hosting accounts.
  1. Open the section "Hosting".
  2. In the block "Extra services" click "Dedicated IP":
  3. Check out the cost information and click "To order":
  4. Pay automatically generated invoice any of available ways and wait for the payment to be credited.
  5. Customize dedicated IP for the desired sites.

You should start setting up a dedicated IP only after the payment has been credited to us.

Important points:

  • A dedicated IP can be connected either to one or to several sites at once within one hosting account.
  • Dedicated IP cannot be set for aliases... They can only be used for main domain and subdomains.
  • Site technical check does not take into account allocated IPs, so it can report that the address record is configured incorrectly, although this is not the case.
  • If the domain is served on third-party NS, you need to make changes to its settings not with us, but in the owner's panel of these NS.
  1. Openup site settings.
  2. Against "IP address" select the dedicated IP from the list and set it instead of the general one:An additional option will appear in the dedicated IP setting field "This site handles direct requests to a dedicated IP address", which can be enabled if the site should accept requests not only by domain name, but also directly by IP (it is better not to enable the option without explicit need):
  3. Edit address records of type A and in the field "Data" specify the set dedicated IP for them:
  4. Disable autoconfiguration of IPv6 in the site settings.
  5. Delete AAAA records in the domain settings, if any.
  6. Wait for the update DNS cache... This usually takes several hours (maximum 24).
  7. Check the site is working.

You can find out the IP address at which the site is opened using the command ping.

After receiving payment for the dedicated IP, all outgoing connections from the hosting account via IPv4, instead of the direct server address, will come from the dedicated IP.

It is important to take into account that when sending a request not to an IP address, but to a domain, servers with IPv6 support may often prefer it instead of IPv4. This may make it seem like the dedicated IP is not being used. To avoid this, force the use of IPv4 on connections to other servers, for example:

  • Use the target server's IPv4 address as the host.
  • In PHP cURL specify via setopt force use of IPv4 for an active session:
    curl_setopt($connection, CURLOPT_IPRESOLVE, CURL_IPRESOLVE_V4);
  • PHP functions using socket context options (e.g. file_get_contents), explicitly specify the IP for the outgoing connection:
    $opts = array(
        'socket' => array(
            'bindto' => 'xxx.xxx.xxx.xxx:0',
    $context = stream_context_create($opts);
    echo file_get_contents('https://example.com/', false, $context);

    Instead xxx.xxx.xxx.xxx specify the required IP available for the site instead of https://example.com/ — the address of the target resource. Use as port 0 — so it will be substituted automatically.