10

I setup a custom domain on GAE using the tutorial at aral balkan to access http;//app.apspot.com at http://app.com. (I can access the app at www.app.com)

The tutorial is pretty old(Sep 2008) and it mentions

Add four Hostnames for the naked domain (i.e., yourdomain.com without the www) and have them point to IP addresses 216.239.32.21, 216.239.34.21, 216.239.36.21, and 216.239.38.21.

I added the required A names to my domain dns, but accessing app.com leads me to a Google 404 page
gae a name 404

I have used naked to www redirection on blogger using a similar method(A names provided by Google Blogger Help) and it has worked for me(it still works). However apart from the article at aralbalkan.com, I have not come across an official source which says that naked to www domain redirection using these IPs works for domains on Google Apps(which GAE uses to manage custom domains).

My Question:

Does anybody use a similar method(A names pointing to Google IPs) to resolve www domains from naked domains for custom domains on GAE? If yes, are the IPs different or am I doing it wrong?

The alternate method that I can think of using is, getting a third party host and pointing the A name of app.com to the IP address of that third party host, followed by placing a 301 redirect script to www.app.com on that host.But that will require me to manage another hosting just for naked to www redirection.

If anyone knows of any easier methods to achieve naked to www redirection on custom domains for GAE, please help.

Update:
Thank you for the answers. If it can be of any help, I am using geoscaling.com for DNS. I have an everydns account too. The domain is on namecheap and namecheap offers a freedns option too.

Update 2

Switched back my dns to namecheap. I guess geoscaling.com does not offer a 301 url redirect(correct me if I am wrong), although it's still a great service. Namecheap offers a 301 URL redirect. Should start working in some time.

abel
  • 2,377
  • 9
  • 39
  • 62
  • Hi abel, can you change the accepted answer? This feature now exists in App Engine. – crb Apr 14 '14 at 11:02

7 Answers7

10

While it's true Google doesn't officially support naked domains, it is possible to make this work using your registrar's DNS and Domain Forwarding tools.

For example, http://conversionsupport.com is hosted on Google App Engine, and GoDaddy is where the DNS is managed. The naked domain redirects to the http://www.conversionsupport.com subdomain using a domain forwarding rule.

Requests for the naked domain result in a 301 redirect to the www subdomain. Some SEO resources claim that using one subdomain is better for ensuring search engines don't see your site's content as being duplicative. This 301 redirect should help ensure that both naked domain and www subdomain are treated the same.

Here is a resource for Setting up URL Forwarding in GoDaddy. Note that while this is intended for Google Sites, I have confirmed that it does work on Google App Engine apps.

UPDATE:

To clarify, the naked domain itself will redirect to the www subdomain. This means that if your users type http://example.com then they'll be redirected to http://www.example.com as is the case with my original example above.

From what I understand, most Google Apps accounts are partnered with GoDaddy. Here are the Instructions from GoDaddy Support on Domain Forwarding Using a 301 Redirect..

GoDaddy Domain Forwarding

jamesmortensen
  • 33,636
  • 11
  • 99
  • 120
9

Naked domains are not supported on App Engine. You need to use www-redirects, as you suggest.

Nick Johnson
  • 100,655
  • 16
  • 128
  • 198
3

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 on hosting http:// content.

Fred Sauer
  • 1,012
  • 9
  • 20
2

As nick says, naked domains are not supported by app engine.

On your point of easier methods to achieve naked to www redirection on custom domains... Some DNS hosts, (for example, dyndns.com) integrate that ability into their DNS control panel. You may check with your DNS provider to see if that is the case.

Bill Lynch
  • 80,138
  • 16
  • 128
  • 173
  • I am using geoscaling.com, I have a everydns account and I can use namecheap's free dns service too. Do any of these offer naked to www redirection/ – abel Jan 31 '11 at 14:07
  • EveryDNS was bought by DynDNS. It looks like they should have ported your account to the DynDNS infrastructure at some point last year. – Bill Lynch Jan 31 '11 at 14:50
0

With all the changes over time, I wanted to post that GAE (at least at the time of this writing) DOES support naked domains. I have this working for wdydfun.com. Follow the directions as mentioned above by Fred Sauer and it will eventually work. I'd love to provide more detail on those steps, but things seem to change frequently. You'll have to click around a bit to find where to set stuff. With the DNS propagation time that can be a bit frustrating. I recommend running 

dig ns <your url>

from the command line to help see what is going on. My "www" domain was resolving to ghs.google.com and my naked domain was resolving to dreamhost where the domain was registered. After filling out the extra "A" records from the google directions, the naked domain eventually started returning different information and it worked. If you are testing this out in a browser, it's worth mentioning that at the time of this writing webkit browsers seem to be pickier than mozilla. My DNS settings:

  A     216.239.32.21
  A     216.239.34.21
  A     216.239.36.21
  A     216.239.38.21
  TXT   google-site-verification=W0rC...fnQ
* CNAME ghs.google.com.

Yours will probably look similar. Unless the directions have changed again. The CNAME value changed since when I first set things up, so if what I'm writing here differs from the directions on Google, trust the directions on Google. HTH.

Eric Parker
  • 17
  • 2
0

Naked domain mapping works from the Google Developers Console.

https://code.google.com/p/googleappengine/issues/detail?id=777

We have added support for custom domains for App Engine from the Google Developers Console, meaning you can now associate a custom domain without first associating that domain with Google Apps.

To access the feature, visit https://console.developers.google.com/ and you will find the option to add a custom domain under App Engine > Settings.

NOTE: Currently we do not support SSL on custom domains created through this method (although we expect to rectify this in a future release). In the meantime, we continue to support SSL (via VIP or SNI) for custom domains that are created through Google Apps, and we continue to provide free HTTPS for all *.appspot.com domains.

crb
  • 8,132
  • 6
  • 37
  • 48
0

Alternatively, you could follow below steps which solves this problem, for sure,

  1. Ping the website you are wanting to forward to, in order to get the IP address if you don't know it.

  2. "Run"; CMD; "ping yourwebsite.com"

    Will display ping data and reply from IP address. Note this address.

  3. Login to Godaddy.com to manage your account or other domain registry site

  4. Go to DNS Control Modify/Add "A Host"

  5. Under "Host" enter: @

  6. Under "Points To" Enter the IP Address you obtained earlier.

  7. You are done! Site is forwarded without the www prefix when entered into address bar.

More details and reference :

http://www.techproceed.com/2014/05/custom-domain-setup-on-blogger-with.html

Snehal Masne
  • 3,403
  • 3
  • 31
  • 51