Not everybody wants a website with a name like SITE.pagekite.me, many already own their own domain names and would rather use those.
In fact, this is recommended - it provides a layer of abstraction and independence between your identity on-line and the PageKite Service. If you use a CNAME, you will more easily be able to move your website to some other solution or provider at a later date, if you so choose.
Obviously we hope you won't ever feel the need to do so, but having the freedom to choose is important.
Let's assume you own domain.com and have a PageKite Service account named you.pagekite.me, and you want www.domain.com to be served over PageKite.
The recommended CNAME-based configuration would involve the following steps:
Step 1. is technically not required, you could also create a CNAME directly on you.pagekite.me. However, by using a separate name, you preserve the ability to later use the two names for different websites on different computers.
How exactly to go about step 2. varies depending on where you bought your domain name. We hope to provide more details on the following, if you can help please feel free to edit these pages or upload screenshots:
Steps 3. and 4 are required to integrate the new name into your PageKite configuration.
Note that if you own domain.com and receive e-mail on that domain, then you can not create a CNAME for the top level domain.com name.
This is due to technical details of how DNS and e-mail interact. Generally you can create a CNAME for any other name (www.domain.com or pagekite.domain.com or my.page.domain.com to name a few), just not for the top level name itself.
Once the DNS records have been created and your PageKite account brought up to date, you need to reconfigure pagekite.py to know about your domain.
This usually requires adding two lines to your configuration file, which would look like this:
(Older versions of
Both lines are needed, as the first will guarantee that the DNS records for domain.you.pagekite.me are kept up to date as your front-ends change, and the second takes care of actually registering and routing traffic for www.domain.com.
(Note that if you want to expose HTTPS or SSH servers you will need to add lines for those as well.)