My Misadventures with Cloud At Cost
-
@Carnival-Boy said:
MangoLassi has basically become a Cloud At Cost forum. Half the current threads are on this!
I feel I'm missing out on the fun
It's an explosion of activity. CloudatCost really took some initiative, they saw that someone was using the product and jumped in of their own accord. It really shows how much attention a vendor can get when they have a product that is applicable to the community and takes the effort to be involved.
-
@Carnival-Boy said:
MangoLassi has basically become a Cloud At Cost forum. Half the current threads are on this!
I feel I'm missing out on the fun
Only a couple of dollars to grab a Dev1 and start playing!
-
@Aaron-Studer said:
Should we have a CloudatCost section? Like we do for xByte?
I'm sure that that would be highly welcomed. Sections of that nature are sponsored, though. That's xByte's actual support forum. There should be a description of how those work somewhere.
-
@Aaron-Studer said:
What do you need cPanel for?
I don't necessarily need it. I currently have several websites hosted elsewhere and I'm trying to get a C@C box setup so that I can move the hosting there.
-
@Danp said:
@Aaron-Studer said:
What do you need cPanel for?
I don't necessarily need it. I currently have several websites hosted elsewhere and I'm trying to get a C@C box setup so that I can move the hosting there.
Just use LA(or nginx)MP on CentOS 7. Cpanel is pretty expensive. you can use open source ones if you really need it.
-
Ok... so I now have a server running Centos 6.5 and VestaCP. How does DNS work on CloudatCost? Do I just reference ns1 / ns2.cloudatcost.com? Can I manage it all from within Vesta?
Reviewing my current setup, it appears that I have GoDaddy handling some sites and others are at the hosting site.
-
DNS is the same anywhere. DNS is always your own thing. Most people here recommend CloudFlare. Your DNS is never affected by your hosting provider. That is completely separate. (Except for Reverse DNS, which is always the cloud provider.)
-
You never point DNS to the provider's DNS servers. You need to have your own DNS service for your domain.
-
@StrongBad -- So, I can setup a free account on CloudFlare. What the advantage / disadvantage of using CF versus GoDaddy, who is my registrar? I guess by using CF, I can manage the DNS without concern for the registrar, which could change and the DNS would be unaffected, correct?
-
@Danp said:
@StrongBad -- So, I can setup a free account on CloudFlare. What the advantage / disadvantage of using CF versus GoDaddy, who is my registrar? I guess by using CF, I can manage the DNS without concern for the registrar, which could change and the DNS would be unaffected, correct?
CloudFare is a CDN, which means if your site goes down, it's cached with them, so the site to the public will appear up, although any new content you published wouldn't be seen until your site went live again.
-
@thanksaj said:
@Danp said:
@StrongBad -- So, I can setup a free account on CloudFlare. What the advantage / disadvantage of using CF versus GoDaddy, who is my registrar? I guess by using CF, I can manage the DNS without concern for the registrar, which could change and the DNS would be unaffected, correct?
CloudFare is a CDN, which means if your site goes down, it's cached with them, so the site to the public will appear up, although any new content you published wouldn't be seen until your site went live again.
Well, that is partially true. CloudFlare is both a DNS host AND a CDN. You can use DNS with or without the CDN. And the CDN can be turned on and off by A or CNAME record. How the CDN behaves can be configured. And new content is normally in seconds. I rarely see a delay even when caching is configured. Like, as fast as I can post and refresh, it is there.
-
@Danp said:
@StrongBad -- So, I can setup a free account on CloudFlare. What the advantage / disadvantage of using CF versus GoDaddy, who is my registrar? I guess by using CF, I can manage the DNS without concern for the registrar, which could change and the DNS would be unaffected, correct?
I always recommend CloudFlare, it's the best DNS host I have found. Your registrar should be ruled out out of hand, your DNS services and your web hosting and/or email hosting and your registrar should always be three discrete services. Doesn't matter who they are, they should never overlap. It's a dangerous loss of critical access if you put them together. Each protects you from the others, unless you make them all one.
-
CloudFlare is the best DNS service that I have used. It's fast and stable, easy interface. And CDN features are included for FREE if you want them!
-
Appreciate all the feedback. From a CloudFare POV, what's the best way to handle multiple TLDs (.com, .net, etc) that resolve to the same website? Do I just add one to CF and then add DNS entries for the others?
-
@Danp no, because that is not how DNS works.
Add each domain to cloudflare as another website.
-
Thanks @JaredBusch!
-
Danp - getting back to your question on what DNS your C@C servers should be using, you can point them toward any DNS servers you want. You'll have to do some performance testing to see which ones offer the best performance for your location.
You could for example use the C@C DNS servers, or you could use Google's 8.8.8.8 and 4.4.4.4.
-
Appreciate all of the input. I now have all of my hosted websites running on my C@C box with CloudFlare handling the DNS. Next step is to shut down my account over at MediaTemple.
Then I've got a ZendTo server that I've been hosting internally that I would like to move to the cloud. Anyone know if I can easily transfer this over to my Centos box? It's currently running on a Ubuntu VM.
-
Likely, but don't know that software specifically. You can get Ubuntu on CloudatCost too if needed.
-
ZendTo seems a bit out of date. They offer packages for Ubuntu 12.04 (several versions old, five in fact.) And CentOS 6, which is a full version behind in the RHEL / CentOS world.
