You can host two SSL websites for Windows XP computers or Android 2.0 smartphones.
These platforms do not support SNI (Server Name Indication), so that each website must be hosted on a separate IP address.
Despite being on the same server you could run 2x NS servers (because you have 2x diff IPs) then you can setup your domains to use them~. Talking about this: some registrars do not care if the IPs are different (they just want different hostnames), while others will check if they resolve to the same IP address.
The other use case I encountered was to avoid a throttle per IP address, with an additional IP your APP can switch to use the first IP, then the second one, then the first, etc.
Potentially you could also run another container with the full TCP ports range [1-65535] without NAT/port mapping (so you can use SSH on port 22 on that other IP as if it was a completely different server).
Comments
FTFY
Deal or no deal
Virmach Deals
You can host two SSL websites for Windows XP computers or Android 2.0 smartphones.
These platforms do not support SNI (Server Name Indication), so that each website must be hosted on a separate IP address.
Accepting submissions for IPv6 less than /64 Hall of Incompetence.
What's so good about SJ?
I don't have one over there before.
It looks like @VirMach finally fixed Looking Glass, but the SSL certificate for https://nyc.lg.virmach.com/ is wrong.
Have the honor of being the crybaby who pays $20 for a 128MB VPS at VirMach in 2023.
It is close to Google/YouTube servers~ (Silicon Valley)
Despite being on the same server you could run 2x NS servers (because you have 2x diff IPs) then you can setup your domains to use them~. Talking about this: some registrars do not care if the IPs are different (they just want different hostnames), while others will check if they resolve to the same IP address.
The other use case I encountered was to avoid a throttle per IP address, with an additional IP your APP can switch to use the first IP, then the second one, then the first, etc.
Potentially you could also run another container with the full TCP ports range [1-65535] without NAT/port mapping (so you can use SSH on port 22 on that other IP as if it was a completely different server).
tokyo looks good now
I bench YABS 24/7/365 unless it's a leap year.