Moving domain to Google App Engine

[Martijn]

I'm investigating the possibilities of Google App Engine for a
website. I've come to the point of moving the website from the old PHP
host to GAE.

The site has it's own domain and e-mail addresses attached to this
domain. Because I don't need the services of the old host anymore, I'd
like to move the domain to Google. The MX-record for the domain is
linked to our own mail server.

Now this is my point of confusion. It's absolutely vital that no e-
mail will be lost during the transfer to GAE. I spent quite some time
reading the boards but I can't really find an answer to my question...

Can anybody tell me how to assure no e-mail goes lost during the
domain transfer?

[Robert Kluin]

Just be sure the MX entries continue pointing to your mail server.
Aside from you creating a CNAME record, GAE will not impact your DNS
at all.

Robert

> --
> You received this message because you are subscribed to the Google Groups "Google App Engine" group.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
>
>

[Martijn]

Thanks for the reply Robert, it's quite clear now.

Just a quick follow-up question: I can also keep my current hosting
provider to host the domain (DNS) only. This way nothing will change
in the MX-records.

If I understand correctly I have to do this next:

- I will have to add the domain to Google Apps
- Make a CNAME record pointing to ghs.google.com there so I can access
my app at www.mydomain.com (or [subdomain].mydomain.com).
- I will have add an A record as well for http://mydomain.com.

Is this correct?

And if I want to add an SSL certificate to https://[subdomain].mydomain.com,
can I do this at the Google Apps or at my old hosting provider?

[Wooble]

On Feb 16, 2:50 am, Martijn <keloys...@gmail.com> wrote:
> Thanks for the reply Robert, it's quite clear now.
>
> Just a quick follow-up question: I can also keep my current hosting
> provider to host the domain (DNS) only. This way nothing will change
> in the MX-records.
>
> If I understand correctly I have to do this next:
>
> - I will have to add the domain to Google Apps
> - Make a CNAME record pointing to ghs.google.com there so I can access

> my app atwww.mydomain.com(or [subdomain].mydomain.com).
> - I will have add an A record as well forhttp://mydomain.com.
>
> Is this correct?
>
> And if I want to add an SSL certificate tohttps://[subdomain].mydomain.com,

> can I do this at the Google Apps or at my old hosting provider?

App Engine doesn't support either hosting naked domains (http://
mydomain.com/) or SSL on non-appspot addresses. To use the naked
domain, you'd want an A record pointing somewhere that does a redirect
to www.mydomain.com (many registrars provide such a service). To use
SSL with your own domain name, I believe your only real option at the
moment is to have a proxy running on a separate server, which is
fairly unattractive.

[Martijn]

Thanks for the reply Wooble.

Seeing SSL is an absolute must for the application, I would really
like this to work, this can stop the entire project if I can't get
this to work.

I'm not going to transfer the domain to Google so would it be possible
to set up the SSL at my DNS host?

On 16 feb, 15:03, Wooble <geoffsp...@gmail.com> wrote:
> On Feb 16, 2:50 am, Martijn <keloys...@gmail.com> wrote:
>
>
>
>
>
> > Thanks for the reply Robert, it's quite clear now.
>
> > Just a quick follow-up question: I can also keep my current hosting
> > provider to host the domain (DNS) only. This way nothing will change
> > in the MX-records.
>
> > If I understand correctly I have to do this next:
>
> > - I will have to add the domain to Google Apps
> > - Make a CNAME record pointing to ghs.google.com there so I can access
> > my app atwww.mydomain.com(or[subdomain].mydomain.com).
> > - I will have add an A record as well forhttp://mydomain.com.
>
> > Is this correct?
>
> > And if I want to add an SSL certificate tohttps://[subdomain].mydomain.com,
> > can I do this at the Google Apps or at my old hosting provider?
>
> App Engine doesn't support either hosting naked domains (http://
> mydomain.com/) or SSL on non-appspot addresses.  To use the naked
> domain, you'd want an A record pointing somewhere that does a redirect

> towww.mydomain.com(many registrars provide such a service).  To use

[Nick Johnson (Google)]

Hi Martijn,

On Wed, Feb 17, 2010 at 11:09 AM, Martijn <kelo...@gmail.com> wrote:

Thanks for the reply Wooble.

Seeing SSL is an absolute must for the application, I would really
like this to work, this can stop the entire project if I can't get
this to work.

You have two options here: You can proxy all requests, as Wooble suggests, or you can redirect users to http://yourapp.appspot.com/ for those pages that need to be secure, which _does_ support SSL.

-Nick Johnson

I'm not going to transfer the domain to Google so would it be possible
to set up the SSL at my DNS host?

On 16 feb, 15:03, Wooble <geoffsp...@gmail.com> wrote:
> On Feb 16, 2:50 am, Martijn <keloys...@gmail.com> wrote:
>
>
>
>
>
> > Thanks for the reply Robert, it's quite clear now.
>
> > Just a quick follow-up question: I can also keep my current hosting
> > provider to host the domain (DNS) only. This way nothing will change
> > in the MX-records.
>
> > If I understand correctly I have to do this next:
>
> > - I will have to add the domain to Google Apps
> > - Make a CNAME record pointing to ghs.google.com there so I can access
> > my app atwww.mydomain.com(or[subdomain].mydomain.com).
> > - I will have add an A record as well forhttp://mydomain.com.
>
> > Is this correct?
>
> > And if I want to add an SSL certificate tohttps://[subdomain].mydomain.com,
> > can I do this at the Google Apps or at my old hosting provider?
>
> App Engine doesn't support either hosting naked domains (http://
> mydomain.com/) or SSL on non-appspot addresses.  To use the naked
> domain, you'd want an A record pointing somewhere that does a redirect

> towww.mydomain.com(many registrars provide such a service).  To use

> SSL with your own domain name, I believe your only real option at the
> moment is to have a proxy running on a separate server, which is
> fairly unattractive.

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

--
Nick Johnson, Developer Programs Engineer, App Engine
Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047

[Martijn]

Thank you Nick, it's quite clear now. I'm going to use the
*.appspot.com domain for the secure connection then. Will the SSL for
my own domain be available anytime soon?

On 17 feb, 16:28, "Nick Johnson (Google)" <nick.john...@google.com>
wrote:
> Hi Martijn,

>
> On Wed, Feb 17, 2010 at 11:09 AM, Martijn <keloys...@gmail.com> wrote:
> > Thanks for the reply Wooble.
>
> > Seeing SSL is an absolute must for the application, I would really
> > like this to work, this can stop the entire project if I can't get
> > this to work.
>
> You have two options here: You can proxy all requests, as Wooble suggests,

> or you can redirect users tohttp://yourapp.appspot.com/for those pages

> that need to be secure, which _does_ support SSL.
>
> -Nick Johnson
>
>
>
>
>
> > I'm not going to transfer the domain to Google so would it be possible
> > to set up the SSL at my DNS host?
>
> > On 16 feb, 15:03, Wooble <geoffsp...@gmail.com> wrote:
> > > On Feb 16, 2:50 am, Martijn <keloys...@gmail.com> wrote:
>
> > > > Thanks for the reply Robert, it's quite clear now.
>
> > > > Just a quick follow-up question: I can also keep my current hosting
> > > > provider to host the domain (DNS) only. This way nothing will change
> > > > in the MX-records.
>
> > > > If I understand correctly I have to do this next:
>
> > > > - I will have to add the domain to Google Apps
> > > > - Make a CNAME record pointing to ghs.google.com there so I can access
> > > > my app atwww.mydomain.com(or[subdomain].mydomain.com).
> > > > - I will have add an A record as well forhttp://mydomain.com.
>
> > > > Is this correct?
>
> > > > And if I want to add an SSL certificate tohttps://[subdomain].
> > mydomain.com,
> > > > can I do this at the Google Apps or at my old hosting provider?
>
> > > App Engine doesn't support either hosting naked domains (http://
> > > mydomain.com/) or SSL on non-appspot addresses.  To use the naked
> > > domain, you'd want an A record pointing somewhere that does a redirect

> > > towww.mydomain.com(manyregistrars provide such a service).  To use

> > > SSL with your own domain name, I believe your only real option at the
> > > moment is to have a proxy running on a separate server, which is
> > > fairly unattractive.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-a...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > google-appengi...@googlegroups.com<google-appengine%2Bunsubscrib e...@googlegroups.com>

[Nick Johnson (Google)]

Hi Martijn,

On Thu, Feb 18, 2010 at 7:24 AM, Martijn <kelo...@gmail.com> wrote:

Thank you Nick, it's quite clear now. I'm going to use the
*.appspot.com domain for the secure connection then. Will the SSL for
my own domain be available anytime soon?

We'd definitely like to provide SSL on custom domains, of course. We're blocked by the requirement for browsers to support SNI (http://en.wikipedia.org/wiki/Transport_Layer_Security#Support_for_name-based_virtual_servers) before SSL on custom domains will work, unfortunately, so we don't yet have a timeline.

-Nick Johnson

To unsubscribe from this group, send email to google-appengi...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.