samedi 3 octobre 2015

AWS - IP Address and DNS Settings on new accounts

I've (hopefully) successfully set up Cpanel on AWS with clustering following the instructions: http://ift.tt/1FNYXva

I've been using CPanel/WHM on a dedicated server for a few years before I set up this new Cpanel installation on AWS. My issues comes from how new accounts are set up differently on a dedicated server vs the AWS way.


My first issue:

When I created a new account on my dedicated WHM, I was provided IP Addresses from the server farm that I assigned to newly created accounts. Once assigned, I can access the site with either the IP or the domain name. Now with this new AWS way, there's no info in the tutorials about how I obtain new IP Addresses. I tried adding a new local IP like 10.0.0.30 (because it says it's in NAT mode and use local IP) and assigning this as a dedicated IP to the newly created accounts but I don't understand how anybody can access the site through that IP since its a local IP. So how do I access the domain through custom IP and domain like I did before? I must be missing something fundamental.


My second issue:

On my dedicated WHM after I created a new account, I would typically go to DNS Functions -> Edit DNS Zone and edit the zone to customize my nameserver as so:

mynewdomain.com ns1.mynewdomain.com ns2.mynewdomain.com

anothersite.com ns1.anothersite.com ns2.anothersite.com

thirdsite.com ns1.thirdsite.com ns2.thirdsite.com

and then in my register I would add these custom nameservers into the register and point them to the dedicated IPs of each domain. But with the AWS way, the only way I was able to set this up was to use the new cluster nameservers as the nameserver for ALL accounts in this new WHM installation.

Like this:

mynewdomain.com ns1.awsnameserver.com ns2.awsnameserver.com

anothersite.com ns1.awsnameserver.com ns2.awsnameserver.com

thirdsite.com ns1.awsnameserver.com ns2.awsnameserver.com

Is this the correct / the only way I can set up accounts now through this set up? Is there a way to have custom nameservers names like I did in dedicated WHM?




Aucun commentaire:

Enregistrer un commentaire