Naturally I discovered a bug in DreamHost's process - I hope they can fix things up. Now I can describe the details of how I moved the first domain and files. In a prior post I described how to obtain a transfer authorization code. I'm continuing the process of moving my Tucows/Lunarpages domains and files to DreamHost. DreamHost tech support was very helpful, though they did have to correct themselves a couple of times. It took a while to understand this, and a bit of time to write it up, but not time at all to do it. So now I had my files section - with FTP services too. I configured that subdomain so anyone entering "would go to "" (a DH configuration setting). I wanted a place to store files - something Google Apps does very poorly. Everything worked as before, except that Lunarpages had broken things and couldn't fix them. I changed the nameserver settings at my registrar (Tucows at the moment) to the, etc settings.I'd made a corresponding change in a Blogger blog, publishing it to "". I manually added the CNAME entry of "".That created almost all the CNAME and MX (mail exchange, see DNS record types) settings in the above image. I used DreamHost's "fully host domain at Google Apps" first.These are totally generic, the traffic gets routed to the right Google Apps because of the matching domain names, not because of anything special in this table. I just had to setup the DNS at DH so it had the right CNAME settings to direct traffic and handle mail. In this case everything was already setup on the Google Apps side, including using Google's now obsolete Page Creator to manage our web pages. You may also see why Google Apps are so loosely related - they are really only bound together at the DNS level. Ok, if you understand all of the above then you're ready to understand how I migrated, and its related Google Apps services, from Lunarpages to DreamHost. It matches this request against the custom URL I assigned my Google Apps calendar through my Google Apps Dashboard, and it renders the correct calendar. When Google gets this transaction it sees it's a request for "". On the other hand, for example, would have to be handled by DreamHost. So the request for effectively goes to Google. As we see in this picture of DreamHost's nameserver the subdomain request is then routed through a CNAME to Google ( ). So the requests go to the DreamHost nameserver. The registrar for knows to send all domain traffic DreamHost nameservers - because I told it to use those nameservers. When I enter "" in my browser, the Internet's DNS system first "asks" where to route the request. Let's walk through an actual transaction. ![]() in your Google Apps you need to setup a custom name that exactly matches the name you created in the CNAME. set up a rule in your nameserver provider's DNS to route all traffic for to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |