Until google releases something similar to elastic ip we're not going to progress this issue and the https on custom domain issue. AFAIK this is the biggest issue for GAE after "make the whole thing reliable".
No one outside google knows the reason they haven't released this feature or indeed if they will. Is it technical, political or resourcing / scheduling? If they do release it it will have to be pay per day / month but we're all ok with that. On Jul 29, 8:32 pm, Peter Petrov <[email protected]> wrote: > How about using SRV records, instead of CNAME? I don't know if the > popular browsers support them, but if yes, they are a perfectly valid > solution. > > On Jul 29, 7:40 pm, "Nick Johnson (Google)" <[email protected]> > wrote: > > > On Wed, Jul 29, 2009 at 5:37 PM, Barry Hunter > > <[email protected]>wrote: > > > > 2009/7/29 Nick Johnson (Google) <[email protected]>: > > > > Hi Daniel, > > > > > We don't support 'naked' domains due to issues with the way DNS works > > > (you > > > > can't CNAME a 'naked' domain). We are actively looking for a way to > > > resolve > > > > this. > > > > It is possible to create a CNAME for a naked domain. Its not widely > > > supported by all DNS hosts though. It does however have the side > > > effect of breaking MX records - so email will not function on the > > > domain. > > > It is in violation of the DNS RFC to create a CNAME record on a name that > > has any other records - that includes an A record for the 'www' subdomain. > > Some clients may be lenient enough to accept it, but it's not something to > > rely on. > > > > Example: > > > >http://centralops.net/co/NsLookup.aspx?domain=vacation-tours.co.uk&ty... > > > > Alas cant make this work with AppEngine, because Google Apps says > > > "Required field must not be blank", when trying to associate it :( > > > > This is what the 123-reg.co.uk admin has to say about it: > > > "Warning - If you have an @ record set to a CNAME, all other @ records > > > (including MX) will be ignored and set to the same domain to which it > > > points." > > > > > There's no limitation on what subdomain(s) you can map your app to, > > > however > > > > - it doesn't have to be 'mydomain' or anything else. Most people map > > > their > > > > app to 'www', and use a service that sends 302 redirects to the www > > > > alias > > > > for any requests made to the naked domain. > > > > > -Nick Johnson > > > > > On Wed, Jul 29, 2009 at 3:08 PM, Daniel Rhoden <[email protected]> > > > wrote: > > > > >> At any of the paid levels or free, is there any better support of > > > >> private domains than just naked domains, mapping <appid> to http:// > > > >> <appid>.yourdomain.com ? > > > > >> For example, lets say I have domain 'mydomain.com' and I registered > > > >> 'mydomain' on App Engine. It would be pretty silly having people go > > > >> to 'http://mydomain.mydomain.com/' > > > > >> So I'm wanting to know, is there a way I can have 'mydomain.com' BE my > > > >> domain for my app? > > > > >> Thanks. > > > > >> Also, will there be any DNS offerings? > > > > >> --Daniel Rhoden > > > >> Guntersville, Alabama > > > > -- > > > Barry > > > > -www.nearby.org.uk-www.geograph.org.uk- > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
