RE: Azure CentOs 7.1 + Sentora
06-01-2015, 07:21 AM
(This post was last modified: 06-01-2015, 07:41 AM by vaso.
Edit Reason: More details..
)
(05-30-2015, 07:33 PM)apinto Wrote: Hello @[vaso], welcome to Sentora
I do not have experience with Azure CentOS (but I'll learn ), however I'll try to help point you in the right direction.
(05-30-2015, 09:16 AM)vaso Wrote: 1) Sentora is asking for "The public IP of the server" when installing. Azure gives a public address called VIP which is virtual. That means that if the server is switched off for a certain time the IP will be released and when the server is on again there will be a new VIP assigned. They recommend to use CNAME rather for this purpose so if anything is pointing to the server it should still work. How this could be used when installing Sentora? Can I use CNAME instead of IP address?
..the Azure CentOS provided me with DNS Name (something.cloudapp.net), which I used as a subdomain and I used VIP at the moment for requested IP address. I can now access Sentora after successful installation through provided DNS Name something.cloudapp.net. I can easily reinstall it if I should rather provide CNAME through installation?
1) From what I understood reading Microsoft Azure Reserved Public page the VIP is the Public IP, it is dedicated and sticky, meaning it will not be changed if the server reboots or is turned off for some period (unless you cancel it).
Microsoft Azure Wrote:The Reserved IP address is sticky, meaning once it’s associated with the cloud service, it won’t change unless you decide to disassociate it.You should install Sentora using the VIP as the Public IP Sentora requests from you.
Regarding the domain, you should use your own dedicated subdomain for sentora (something like panel.domain.tld).
______
(05-30-2015, 09:16 AM)vaso Wrote: 2) I couldn't find any information regarding this situation. I have got a domain registered with GoDaddy and would like to host website on the server above. I created in GoDaddy new record for mywebsite.com:
dns entry - cms
type - CNAME
destination - something.cloudapp.net
Is this just going to work in Sentora when I add my new domain cms.mywebsite.com in Sentora Domain Management -> Domains or I still need to create DNS in the Sentora DNS Manager? This is a bit confusing..I think in zPanel it would be just working pointing the domain to the zPanel?
2) The Setup you refer should work (CNAME entry pointing to your Azure subdomain).
If you are using GoDaddy as your Name Server you have no need to use Sentora DNS, just ignore it; Everything you setup in Sentora DNS will have no effect because your domain is being managed by GoDaddy (and I would leave it that way for now).
DNS is a complicated area and require a lot of research to understand (research that I strongly suggest you to do), it's normal you feel confused.
_____
By the way, are you using Sentora or Zpanel? At this point you should be using Sentora
One last thing, I would suggest you to try different configs and see what works and what does not work, just reinstall the server if something is not working, this is probably one of the best ways to learn.
Hope this has helped you, but take everything with a grain of salt as, like I said, I do not have experience with Azure.
Thank you apinto
This is an update:
- Yes, I use Sentora!
- The CentOs on Microsoft Azure I am using for testing, the basic configuration cost me so far £1 per 6 days, it is pays as you go option, probably worth to play for everybody!
- The installation I used for Sentora was manual 7 steps and with no problems
- The one command installation weren't working (some errors I didn't understand)
- The IP or VIP was done as you suggested, thank you for that, all clear
- The CNAME was working and I can access the page, thanks DNS is indeed complicated and I didn't touch it as it is working as you suggested
- I have added as my first domain to Sentora this cms.mywebsite.com and that is working perfectly
- I wanted to add another domain called cms2.mywebsite.com and get this error message "You cannot add a Sub-Domain here. Please use the Subdomain manager to add Sub-Domains."
- Obviously if I go to subdomain it will only allow me doing cms2.cms.mywebsite.com which I don't want
- I tried to add to domains cms.blabla.com and that was working
- You can add any subdomain.domain.com to the domains if there is not already such a domain but if you would like to add another subdomain2.domain.com you cannot
- I didn't want to add just domain.com and then use sub domains manager as my main domain is used on another server
Thanks again!
UPDATE on the problem - This is really cool to learn and find out things..
So I don't know if the issue is real issue but this is what I did
- Simply I removed my only domain cms.mywebsite.com and added just mywebsite.com regardless that this domain is not actually pointing to this server
- I added subdomains cms and cms2 and all is working well