Enhance Flexibility with Additional IPs

By default, Shared and Reseller hosting accounts are assigned a single shared IP address, without a dedicated one. You can easily locate your site's current shared IP address in the General Information section of your cPanel.

• Shared IP Address : A shared IP address means that multiple websites use the same IP address. While this is the most common setup, it allows your website to share resources with other sites on the same server. The web browser interacts with the DNS and the server to ensure the correct website loads. With a shared IP, it’s common for hundreds of sites to share the same address.
• Dedicated IP Address : A dedicated IP address is unique to your website and isn’t shared with any other sites. Even though your site may be hosted on the same server, your dedicated IP ensures exclusive access. This can be beneficial for certain use cases, such as SSL certificates, custom email configurations, or better control over server-level settings.

The Failover feature with Additional IP addresses, also known as Failover IP or Floating IP, ensures high availability and service continuity for your applications and systems. With this feature, you can quickly reassign IP addresses from one server or service to another, minimizing service interruptions for your users. This functionality is especially useful during service migrations, transitioning projects from development to production, or switching to a backup server in case of an incident.

Additional IP addresses are available in both individual IPs (/32) and larger IP blocks (up to /24), offering you the flexibility to manage your infrastructure more effectively and maintain uptime during critical operations.

A RIPE IP address refers to an IP address that is managed and distributed by RIPE NCC (Réseaux IP Européens), the authority responsible for IP address allocation and management across Europe. RIPE is an open community that plays a key role in maintaining and developing the global Internet infrastructure. One of its primary functions is to allocate IP address blocks to European Internet Service Providers (ISPs) and maintain a public database that includes crucial information like country-specific IP ranges, current IP allocations, and geolocation data. This helps ensure the effective and organized distribution of IP addresses across Europe.

An ARIN IP address is an IP address managed by the American Registry for Internet Numbers (ARIN), which oversees the allocation and management of IP addresses in North America, including the United States and Canada. Similar to how RIPE operates in Europe, ARIN is responsible for ensuring the proper distribution of IP address blocks to ISPs and maintaining a public registry of IP address allocations. This system helps streamline Internet services across the region and ensures proper address management.

If your Additional IP is found to be blacklisted (RBL) upon release, ServerMO reserves the right to apply a 10-euro fee as stated in our Terms and Conditions. This fee helps cover the costs of unblacklisting the IP and ensuring it is properly cleared for future use.

If your Additional IP address or block of IPs remains unassigned to a service for 30 consecutive days, ServerMO reserves the right to reclaim the IPs after notifying the user. For more information, please refer to the Terms and Conditions for Additional IP.

If your Additional IP address or block of IPs remains unassigned to a service for 30 consecutive days, ServerMO reserves the right to reclaim the IPs after notifying the user. For more information, please refer to the Terms and Conditions for Additional IP.

No, Additional IPv6 blocks are specific to a region due to the hierarchical design of IPv6 address space. However, you can still re-route the blocks to any other vRack-connected backend.

Yes, you can use the same vRack with IP blocks in multiple locations, but it’s important to check the limitations and proceed with caution.

To disable SLAAC, you can turn it off within the Control Panel or by making an API call for each Additional IPv6 block. This option is available for the first /64 subnet of the block.

Additionally, to ensure your hosts do not automatically reconfigure IPv6 addresses, you can apply the following sysctl configurations either globally or per interface:

• ipv6.conf.all.autoconf=0
• net.ipv6.conf.all.accept_ra=0

This will prevent your operating system from automatically reconfiguring the interface's IPv6 address or default routes.

Yes, any IP blocks released during the Alpha/Beta stages will continue to operate after reaching General Availability (GA).