LightCMS Upgrading to New Datacenter!

PLEASE NOTE: On April 30th the date of the Datacenter upgrades described in this post was updated from May 5, 2014 to June 2, 2014.

We’re pleased to announce that we are migrating the LightCMS system to a beautiful, new home inside one of NetSuite’s Datacenters. As you know, NetSuite is the parent company of LightCMS and we are very excited that this change will locate the LightCMS servers inside a Datacenter over which our company has control.

New Datacenter Upgrade

This arrangement holds many distinct advantages over our current situation. NetSuite and LightCMS will now have control over physical server security, maintenance and scheduling as well as the ability to improve our monitoring capabilities and scale more rapidly. Additionally, LightCMS servers will now gain access to NetSuite’s global load-balancing infrastructure which has the potential to improve system performance in some locations around the world. This move also sets us up for potential expansion to multiple data centers in the future.

Our team is already hard at work ensuring this transition goes as smoothly as possible. Our goal is to make the change as seamless as possible for you and your clients. However, due to the nature of this change, there are a couple of items that may affect you or may require action on your part. Please read the details below to ensure you are aware of all that is happening.

Scheduled Downtime - June 2, 2014

12:01am to 4:01am CDT (GMT -5)

In order to ensure the server transition goes smoothly, we must take the LightCMS system offline entirely while we make the move. The maintenance window listed above reflects the time we plan to make this transition. When we bring the system back online at the end of this window, LightCMS will be operating on its new servers.

IP Address Update Required for Custom Domains

Moving Datacenters means that LightCMS’s IP address will change. This means if you are using custom domains with your LightCMS websites, you will need to update the IP addresses for those domains AFTER we have made the move on June 2nd. Don’t worry, your websites will continue to function even if you don’t make these updates. However, custom domains that are not updated after the move will resolve to their associated *.publishpath.com domains.

Changing your IP address means updating the Address Records for your custom domains. You must do this using tools provided by your DNS provider (GoDaddy, BulkRegister … etc.). When you originally set up a domain to work with LightCMS, you would have created an address record to point to LightCMS’s IP address. Now, you’ll simply be editing that address record to point to a new IP.

The new IP address you will need to use AFTER we make the change on June 2nd is: 64.89.44.97

IMPORTANT: Do NOT make any domain changes now. You should make these changes after we move LightCMS to its new home on June 2, 2014.

To help you with this transition, we’ve created a handy support article about the changes you’ll need to make. Please take a look and if you still have questions, feel free to email us anytime at support@lightcms.com and we’ll get back to you right away.

Thank you for your support of LightCMS. We look forward to continuing to serve as your website partner for years to come.

18 comments (Add your own)

1. Hank Kingston wrote:
I am not sure, but can you check to see if our domain and IP address will have to be changed?

Domain: stpaulsec.org
IP Address: 75.126.211.188

Respond to hkingsto@frontiernet.net

Mon, April 7, 2014 @ 8:12 AM

2. Tim wrote:
Hi Hank, yes your domain is using our current IP address. This will need to be updated after we move Datacenters on May 5.

Mon, April 7, 2014 @ 8:14 AM

3. Jim Sproull wrote:
What is the new IP address?

Thu, April 17, 2014 @ 10:16 AM

4. Tim wrote:
Hi Jim, I've just updated the article with the new IP address, which is 64.89.44.97 - please remember you should NOT make any changes to your DNS records prior to May 5, 2014.

Thu, April 17, 2014 @ 1:47 PM

5. Ryan Herring wrote:
Same question as Hank. Can you see if ours will need updating as well?

Thu, April 24, 2014 @ 10:55 AM

6. Tim wrote:
Hi Ryan,

Every custom domain that points to the LightCMS or Radium3 platform will need to be updated following the move. It appears that herringconstructioninc.com is pointing to our platform so it will need to be updated on May 5th. Your site will continue to function even if you don't make the change, but your custom domain will redirect to your *.publishpath.com until the custom domain is updated.

Thanks!
Tim

Thu, April 24, 2014 @ 11:01 AM

7. Edwin Davidson wrote:
Is there a reason we can't use a CNAME pointing to ourdomain.publishpath.com instead of an A record pointing to your IP?

I understand that some DNS servers do not support a CNAME for the DNS zone apex, however mine do. CloudFlare and Amazon Route 53 both support this, for example.

If we could do this, we could simply CNAME our DNS now and it would automatically change whenever you modify *.publishpath.com DNS after the TTL expires.

Edwin

Thu, April 24, 2014 @ 1:17 PM

8. Tim wrote:
Hi Edwin,

The problem with CNAME is that, at least in most cases, CNAMEs cannot be used for the root of a domain. So, for example, you can set up a CNAME for www.yourdomain.com but not for yourdomain.com. The A Record is required for the root level control.

If you wish to use a CNAME, you can point it to domain.publishpath.com. That is a special domain we set up which currently points to our current address and which we will update to the new address at the point of the change. You can try setting your domains up this way, but again, the issue we have found in the past is that it will be insufficient if you want root-level control.

I hope this helps.

Thanks!
Tim

Thu, April 24, 2014 @ 2:02 PM

9. Edwin Davidson wrote:
Tim, thank you.

I currently have my domain zone apex primeinc.com and the host www pointed to an HA pair of load balancers. These load balancers are pointed to two DNS records; CNAME primeinc2.publishpath.com and an Amazon Cloudfront distribution I have configured. The load balancers monitor both connections and only serve data from a source if it is returning the results I expect (no HTTP errors, certain unique text is in the HTML.)

My Cloudfront distribution points back to primeinc2.publishpath.com and has all of my DNS names configured as alternate domain names.

My Amazon Cloudfront distribution has a lot of cache settings in place allowing Cloudfront to cache my site for a long time should primeinc2.PublishPath.com be unavailable.

If I have done everything correctly, my static portion of my website should remain up during your transition by means of the Cloudfront cache. I will not be able to edit it, nor will the shopping cart function, but the bulk of it should stay up. If I have done everything right, then my load balancers and Cloudfront distribution will resume serving content from Publishpath once the DNS has been updated.

Cloudflare would be another, simpler way to do the same thing.

Thu, April 24, 2014 @ 3:05 PM

10. David wrote:
I've just been made aware of this. This is a pretty big undertaking as we have over 40 clients who have a custom domain name that we don't manage. This will mean that we will have to re-gain access to 40 godaddy or network solutions accounts. Stupid question. Will the old IP address work for a few days after May 5th or once you make the change all custom domains stop showing sites altogether?

Mon, April 28, 2014 @ 11:12 AM

11. Tim wrote:
Hi David. Your custom domains will still function, even if you do not make changes to the IP address after May 5th. The only difference is that custom domains directed to the old IP address will redirect to their associated *.publishpath.com domains.

Mon, April 28, 2014 @ 12:45 PM

12. Brenda Anderson wrote:
Hi Tim,

Would you please tell me if our IP address will have to change, and if so, is that something that we would have to do here? Thanks!!

Tue, April 29, 2014 @ 2:59 PM

13. Tim wrote:
Brenda, if your website runs on LightCMS or Radium3 then yes your domain will need to be updated. It is something you will have to do on your end as we don't have control of your DNS. If you need help, our support team will be glad to assist you. Please contact them at support@lightcms.com

Wed, April 30, 2014 @ 10:41 AM

14. Tim wrote:
PLEASE NOTE: the date of the upgrades has been postponed from May 5th to June 2nd. The post above has been updated with the new date but some of the comments still say May 5th. Please do not make any changes to your DNS until after we make the upgrades on June 2nd. If you have any questions, our support team is ready to assist you at support@lightcms.com.

Wed, April 30, 2014 @ 10:43 AM

15. Jack wrote:
Tim: Sort of confused. If you are hosting our site, how and where do I change our DNS?

Mon, May 5, 2014 @ 12:22 PM

16. Tim wrote:
Hi Jack. We are hosting your website but we don't control the domain name you use with your website. You or someone at your organization would have registered the domain name with a domain registrar such as GoDaddy or BulkRegister. The domain is what must be updated to point to our new servers after we make the move on June 2. If you have further questions, please feel free to contact our support team at support@lightcms.com any time and they can help to talk you through it.

Mon, May 5, 2014 @ 12:47 PM

17. Hyacinth Wright wrote:
Good morning will the www.mtzionofalbany.org require this change?

Thanks,

Mon, June 2, 2014 @ 7:55 AM

18. James Cunningham, nbass@bcacct.org wrote:
We have a very simple site that we are not sure how it is hosted. Could you take a look at our site and let us know?

Tue, June 3, 2014 @ 9:16 PM

Add a New Comment

Enter the code you see below:
code
 

Comment Guidelines: No HTML is allowed. Off-topic or inappropriate comments will be edited or deleted. Thanks.

Tags

Archive

Try it yourself. It's free.

Takes less than 60 secondsNo commitmentNo payment information required

Sign Up for Free