Allow for assigning different IP addresses for subdomains under a webspace. Right now, you cannot do this.
For example:
Existing Platform:
Webspace Name: joker.com, IP assigned, shared 2.2.2.2
2 Subdomains are needed: life.joker.com, and death.joker.com
However, Life.joker.com is going to use 2.2.2.2 shared IP as that is a wordpress page.
Death.joker.com is going to be a web app hosted by, let's say....codeignite, and we don't want it to have to use the same IP address as the main site. Instead, we want to use 2.2.2.3
Right now, we cannot do this. In the current plesk iteration, the subdomains of a web space, can only inherit the same IP address as the webspace, which makes management of large webspaces....difficult.
There are many times in which a company would like to have different IP address spaces assigned to their subdomains - especially for corporate/enterprise companies who have 11+ web properties and different services on each root web property.
A good use case example would be something like this for a typical corporation.
Webspace Name: joker.com
The company has services that offer:
- Corporate Website
- Corporate event planning website
- Corporate File Share
- Corporate Training Site
- Corporate HR site
- Corporate CRM site
- Corporate Project Management site
- Corporate Teams Site
Now, if they were to do this in Plesk, even Plesk for windows, ALL of those services would share the same IP address as the parent workspace.
When in reality, it should be separated based on the services offered.
Why? There are drastic differences between technologies in play here, from different frameworks to different services. Having them physically separated from each other on the hosting platform, as well as on the IP platform makes tracking their service's easier, and tracking logging, offline time, and redundancies far more easier than if they were all using a single '2.2.2.2' ip address. Mainly because doing HTTP monitors isn't as reliable as doing ping monitors.
Phillip
Allow for assigning different IP addresses for subdomains under a webspace. Right now, you cannot do this.
For example:
Existing Platform:
Webspace Name: joker.com, IP assigned, shared 2.2.2.2
2 Subdomains are needed: life.joker.com, and death.joker.com
However, Life.joker.com is going to use 2.2.2.2 shared IP as that is a wordpress page.
Death.joker.com is going to be a web app hosted by, let's say....codeignite, and we don't want it to have to use the same IP address as the main site. Instead, we want to use 2.2.2.3
Right now, we cannot do this. In the current plesk iteration, the subdomains of a web space, can only inherit the same IP address as the webspace, which makes management of large webspaces....difficult.
There are many times in which a company would like to have different IP address spaces assigned to their subdomains - especially for corporate/enterprise companies who have 11+ web properties and different services on each root web property.
A good use case example would be something like this for a typical corporation.
Webspace Name: joker.com
The company has services that offer:
- Corporate Website
- Corporate event planning website
- Corporate File Share
- Corporate Training Site
- Corporate HR site
- Corporate CRM site
- Corporate Project Management site
- Corporate Teams Site
Now, if they were to do this in Plesk, even Plesk for windows, ALL of those services would share the same IP address as the parent workspace.
When in reality, it should be separated based on the services offered.
- Corporate Website: 2.2.2.2
- Corporate event planning website: 2.2.2.2
- Corporate File Share: 2.2.2.3
- Corporate Training Site: 2.2.2.4
- Corporate HR site: 2.2.2.5
- Corporate CRM site: 2.2.2.5
- Corporate Project Management site: 2.2.2.6
- Corporate Teams Site: 2.2.2.7
Why? There are drastic differences between technologies in play here, from different frameworks to different services. Having them physically separated from each other on the hosting platform, as well as on the IP platform makes tracking their service's easier, and tracking logging, offline time, and redundancies far more easier than if they were all using a single '2.2.2.2' ip address. Mainly because doing HTTP monitors isn't as reliable as doing ping monitors.
Regards!