Naked and www custom domains with Google App Engine

1
votes

I have added two custom domains to Google Developers Console for a Google App Project. One, a naked domain with A and AAA records set on the third party DNS manager as specified by Google. Two, a www domain with a Cname record set on the third party DNS manager, as specified by Google.

The www is serving, but the naked domain is not! The A records ip addresses timeout on my local machine but I get results when using http://tools.pingdom.com/ping/

Obviously you can use more than one custom domain but is there something I'm missing here?

1
google-app-enginednscnamea-records
Possible duplicate of How to use Google app engine with my own naked domain (not subdomain)? - Dan Cornilescu

1 Answers

0
votes

Update: custom naked domain mapping is now supported directly in GAE, see How to use Google app engine with my own naked domain (not subdomain)?.

[Old answer follows]

If it's acceptable for you to use custom domains through Google Apps then you can use the Google Admin console to:

  • map your naked domain to Google Apps
  • redirect the naked domain to a certain (sub)domain of your choice

I find several advantages of going this way:

  • you can change the naked domain redirect without any change in the GAE apps domain configs

  • the direct domain mapping of GAE apps (without using Google Apps) is still very young, documentation is far from exhaustive

  • you can use SSL with your custom domains, according to the docs: "To add Secure Sockets Layer (SSL) encryption (i.e., an HTTPS address) to your App Engine app, you must use the SSL service provided with Google Apps".