Is there a way or could it be implemented a solution to use i-mscp in to an Openstack / Amazon EC2 enviroment.
As you probably know, the virtual machines inside this kind of cloud does not have a public IP. On the VM there is a private ip, and to acces the outside Internet uses a kind of NAT.
i-mscp on cloud (openstack - amazon ec2)
- Delta04
- Closed
- Thread is marked as Resolved.
-
-
i-MSCP runs fine behind NAT if you configure it correctly.
I have been running it behind NAT since forever, and I haven't had any "real" problems. But I can't tell you if it works in an cloud environment.
-
-
Thanks for the answer.
Is there any specific setting or modification that I have to apply on the i-mscp so that it would work behind NAT?
-
No I wouldn't say so, mine worked pretty straight out of the box. Just remember that DNS can be a little challenging, since you are behind NAT and want to use i-MSCP as DNS server.
-
-
That is what I was thinking about. The DNS part with the SPF and all that. Probably must be configured with the public ip.
-
If you want it working correctly, then yes =).
-
-
I-mscp works great behind NAT, in cloud environment, if there are made some manual changes on the DNS tpl files. To be more exactly, you will have to modified in /etc/imscp/bind/parts , for domains db.tpl file and and for subdomains db_sub.tpl files.
For db.tpl, instead of {BASE_SERVER_IP}, {DOMAIN_IP} you must write your public IP. Also, in the DNS servers area, from
; dmn NS A entry BEGIN
ns{NS_NUMBER} IN {NS_IP_TYPE} {NS_IP}
; dmn NS A entry ENDING
to
; dmn NS A entry BEGIN
ns1 IN {NS_IP_TYPE} xx.xx.xx.xx
ns2 IN {NS_IP_TYPE} yy.yy.yy.yy
; dmn NS A entry ENDINGwhere xx.xx.xx.xx is your master DNS server IP and yy.yy.yy.yy secondary DNS server IP.
To make the sub-domains working, replace {DOMAIN_IP} with your public IP.
Tested on version i-MSCP 1.1.2.