How can you justify the need for more than one IP address per virtual server?

Question

System administration

To obtain additional IPs, you need to prove to RIPE that these IP addresses are really needed. My question is this: How can you justify the need for more than one IP address per virtual server? Perhaps you have examples from personal experience that are somehow related to the feature of the software / software architecture where you need to have two IP addresses.

Answer 1

For two applications (website, service, server) to work with different SSL certificates, different IP addresses are needed.

Answer 2

Another option is to chalk it up to safety. That one IP is public with public services (web), and the second is secret for administration (ssh, mysql, etc.).
There is also a real need to switch from one IP to another in the case of DDOS (there must be one address unknown to anyone to which traffic can be proxied through gates).

Answer 3

You can try to request 2 addresses for DNS servers, though from different subnets.

Answer 4

Does RIPE already issue separate IP addresses?
At one time, when they allocated blocks to a company, they simply wrote “For developer services”, “For QA services”, “For public facing servers”, etc. There, in my opinion, it was enough just to indicate the intended use of the pool and not to paint each address separately.
If you want to prove exactly the need for several IPs per server, then argue with the presence of several different services available via SSL (several different “development environments” or hosting for clients)

Answer 5

If you have several web services in the local area, on different servers and different platforms that need to be released outside and it is desirable that each of them be on a standard port (it is more convenient for users), then it is convenient to push each service through a separate IP. For example CRM, ERP and some news portal, some of them on iis and some on apach.

Answer 6

additional IP addresses are needed, for example, for hot backup or balancing. At the same time, the servers themselves have their own fixed addresses, and each service has an address that is assigned to the master as an alias.

Answer 7

1) virtualization
2) 2 valid SSL certificates for different domains (they have SNI for verification, but still they understand that 30-40% of user machines do not support it)
3) the same services hanging on the same port. I managed to beg for 2 ejabberd, for example.
About all security issues (a la, I want ssh on a separate IP) - forget it right away, they will refuse. About all SEO goals (I have a lot of sites, blablabla) - also immediately forget.
In general, as practice shows, the most reliable option is virtualization. No one asks unnecessary questions later, nothing is needed to prove intentions.
In RIPE, this option will not work, of course, but it flies away for a sweet soul for hosters.

Answer 8

and you can change the hoster to one that gives 2 ip at once, for example, I have BurstNet and I'm happy with it. True, in the USA and the ping there is large, but on the whole it suits me.

Answer 9

dns support

Answer 10

the need for two web servers.
proxying through light or enginix is ​​not always possible in the case of streaming and self-written services in python, for example. Next to the usual Apache or Tomcat, of course.