6

I created a new App and was able to map www.sitename.com to my google app. Once upon a time you could also "redirect the naked domain" name in the google apps domain admin (i.e. sitename.com) but this does not appear to be possible in the admin console any more. The button button to do this is missing now. Any ideas where it went?

I can get the site to come up no problem when I call the www.sitename.com address, however if I request the sitename.com I get a 404 error page from GAE.

I've tried setting up A records with the bare domain pointing to google, but this does not seem to be working.

Is is even possible to make a naked domain to google apps anymore. Any ideas of anything else I can try? Has anyone else ran into this issue in lately?

I'm using Netfirms and they provide DNS for for my domains too. I don't seem to have url forwarding on Netfirms.

rhart
  • 121
  • 2
  • 5
  • This looks like a bug. I saw it a couple of days ago on the domain settings page, but I don't see it anymore. – dragonx Oct 11 '12 at 21:07
  • Even says it's supposed to be there in their own docs ... but alas it is not .. http://support.google.com/a/bin/answer.py?hl=en&answer=2518373 – rhart Oct 11 '12 at 21:27
  • It is not possible anymore. But there is a solution: http://blog.notdot.net/2009/12/Naked-domains-on-App-Engine or your domain provider can redirect. – voscausa Oct 11 '12 at 21:35
  • Possible duplicate of [How to use Google app engine with my own naked domain (not subdomain)?](http://stackoverflow.com/questions/817809/how-to-use-google-app-engine-with-my-own-naked-domain-not-subdomain) – Dan Cornilescu Apr 22 '16 at 01:26

3 Answers3

6

Naked domain (e.g. yourdomain.com) support for App Engine can be setup in three steps:

  1. Setup a naked domain redirect to a subdomain of your choice (e.g. redirect mydomain.com -> www.mydomain.com). See the App Engine FAQ, which instructs you to configure the redirect via the Google Apps control panel for your domain.

  2. Configure App Engine to serve traffic for your custom subdomain (e.g. www.yourdomain.com) via the Google Apps control panel.

  3. (Optionally), setup SSL for your custom domain. This step is required if you which to serve https traffic, but not required if you only plan

Fred Sauer
  • 1,012
  • 9
  • 20
  • I done this but some of my users don;t seem to be able to access the site. Using http://just-ping.com/ reveals the naked domain works fine but not the subdomain. – Tom Larkworthy May 28 '13 at 09:32
1

Just found the link is missing for a new domain I'm trying to set up for Appengine.

Hopefully Google make the link re-appear, otherwise you'll need a web server somewhere that you can get to do the forwarding for you.

  • Set up a DNS A record to point example.com to the IP adress of your web server.

  • Configure your webserver to do a permanent redirection of example.com to www.example.com. This will depend on your web server - for Apache, add a virtual host file to sites-available like this:

    <VirtualHost *>
    Redirect permanent / http://www.example.com/
    servername example.com
    ServerAdmin webmaster@example.com
    ErrorLog /var/log/apache2/error.log
    CustomLog /var/log/apache2/access.log combined
</Virtualhost>

    Google for more details for your web server.

FoxyLad
  • 1,616
  • 11
  • 12
1

here's what i'm doing. i bought a domain name (and that's it) from mediatemple. i wanted a naked url redirect (example.com -> www.example.com) but GAE's naked URL redirect will only work if your site is being served from www.example.com. in my case, my site/app was actually being served from GAE itself, so the naked URL redirection will not work (see the little caution paragraph at the top of this page: http://support.google.com/a/bin/answer.py?hl=en&answer=2518373)

however, the stackoverflow answer at this link (http://bit.ly/10zA67m) pointed me to wwwizer.com which is a free service that allows simple naked url redirects. i just set it up and it seems simple enough. i'm not yet certain if it's working (i just updated the dns zone file a few minutes ago), but if it does end up working, this service will help me out a lot.

UPDATE
after a few hours, the naked url redirecting provided by wwwizer.com is working. sweet! reliability is TBD, but i'm hopeful.

Eric S.
  • 320
  • 2
  • 11
  • 1
    I know this is old but i really want to point out that using a service like wwwizer defies the purpose of SSL entirely. If your app actually requires SSL this is *not* an alternative. Why? You're giving your certificate to a third party service that decrypts all traffic and proxies it to your actual host. Is it just me or does anyone else hear alarm bells? – konqi Aug 04 '14 at 14:06