Cannot create naked or alternate domains for my GAE app.
4 views
Skip to first unread message
Jonathan Feinberg
Jul 30, 2008, 11:05:09 AM7/30/08
to Google App Engine
I have created the mywordle GAE app.
I have created the mywordle google apps domain, in order to point
mywordle.net atthe GAE app.
I bought the mywordle.net domain through Google Apps, and the godaddy
cnames and anames are
all configured correctly by google, such that the mywordle.net name
and its various cnames all work as expected.
I can create the GAE app as a service in google apps, with a dumb
default URL of mywordle.mywordle.net.
When I attempt to add either of www.mywordle.net or mywordle.net, the
submission fails silently. The new names aren't added, and no error
message is displayed.
The mysterious thing is that I was able to do this for http://wordle.net/
, but cannot for the life
of me do it for this new one. What am i missing?
I have created the mywordle google apps domain, in order to point
mywordle.net atthe GAE app.
I bought the mywordle.net domain through Google Apps, and the godaddy
cnames and anames are
all configured correctly by google, such that the mywordle.net name
and its various cnames all work as expected.
I can create the GAE app as a service in google apps, with a dumb
default URL of mywordle.mywordle.net.
When I attempt to add either of www.mywordle.net or mywordle.net, the
submission fails silently. The new names aren't added, and no error
message is displayed.
The mysterious thing is that I was able to do this for http://wordle.net/
, but cannot for the life
of me do it for this new one. What am i missing?
Eric Gillingham
Jul 30, 2008, 1:23:49 PM7/30/08
to Google App Engine
After buying a new domain myself through google and enom, I'm having
the same issue. www.domain works fine but just domain always gets
redirected, hard HTTP 302, to www.domain
On Jul 30, 8:05 am, Jonathan Feinberg <e.e.c...@gmail.com> wrote:
> I have created the mywordle GAE app.
>
> I have created the mywordle google apps domain, in order to point
> mywordle.net atthe GAE app.
>
> I bought the mywordle.net domain through Google Apps, and the godaddy
> cnames and anames are
> all configured correctly by google, such that the mywordle.net name
> and its various cnames all work as expected.
>
> I can create the GAE app as a service in google apps, with a dumb
> default URL of mywordle.mywordle.net.
>
> When I attempt to add either ofwww.mywordle.netor mywordle.net, the
the same issue. www.domain works fine but just domain always gets
redirected, hard HTTP 302, to www.domain
On Jul 30, 8:05 am, Jonathan Feinberg <e.e.c...@gmail.com> wrote:
> I have created the mywordle GAE app.
>
> I have created the mywordle google apps domain, in order to point
> mywordle.net atthe GAE app.
>
> I bought the mywordle.net domain through Google Apps, and the godaddy
> cnames and anames are
> all configured correctly by google, such that the mywordle.net name
> and its various cnames all work as expected.
>
> I can create the GAE app as a service in google apps, with a dumb
> default URL of mywordle.mywordle.net.
>
> submission fails silently. The new names aren't added, and no error
> message is displayed.
>
> The mysterious thing is that I was able to do this forhttp://wordle.net/
> message is displayed.
>
WallyDD
Jul 30, 2008, 2:30:54 PM7/30/08
to Google App Engine
Combining dns with Google Apps isn't the most fun. Even if it's right
you have to wait 24/48 hours to convince yourself. And sometimes it
still fails to work, so you have to do it all again.
From memory;
1. I created temp.domain.com in google apps.
2. Added domain.com to the app/domain
3. Added www.domain.com to the app/domain
3. Pointed the A records to googles numbers. (in godaddy)
4. Linked the www record to ghs.google.com (in godaddy)
5. Waited 24/48 hours found it didn't work.
6. Removed the www.domain.com link from the app/domain, then added it
again.
Hope this helps.
On Jul 30, 11:05 pm, Jonathan Feinberg <e.e.c...@gmail.com> wrote:
> I have created the mywordle GAE app.
>
> I have created the mywordle google apps domain, in order to point
> mywordle.net atthe GAE app.
>
> I bought the mywordle.net domain through Google Apps, and the godaddy
> cnames and anames are
> all configured correctly by google, such that the mywordle.net name
> and its various cnames all work as expected.
>
> I can create the GAE app as a service in google apps, with a dumb
> default URL of mywordle.mywordle.net.
>
> When I attempt to add either ofwww.mywordle.netor mywordle.net, the
you have to wait 24/48 hours to convince yourself. And sometimes it
still fails to work, so you have to do it all again.
From memory;
1. I created temp.domain.com in google apps.
2. Added domain.com to the app/domain
3. Added www.domain.com to the app/domain
3. Pointed the A records to googles numbers. (in godaddy)
4. Linked the www record to ghs.google.com (in godaddy)
5. Waited 24/48 hours found it didn't work.
6. Removed the www.domain.com link from the app/domain, then added it
again.
Hope this helps.
On Jul 30, 11:05 pm, Jonathan Feinberg <e.e.c...@gmail.com> wrote:
> I have created the mywordle GAE app.
>
> I have created the mywordle google apps domain, in order to point
> mywordle.net atthe GAE app.
>
> I bought the mywordle.net domain through Google Apps, and the godaddy
> cnames and anames are
> all configured correctly by google, such that the mywordle.net name
> and its various cnames all work as expected.
>
> I can create the GAE app as a service in google apps, with a dumb
> default URL of mywordle.mywordle.net.
>
> submission fails silently. The new names aren't added, and no error
> message is displayed.
>
> The mysterious thing is that I was able to do this forhttp://wordle.net/
> message is displayed.
>
Eric Gillingham
Jul 31, 2008, 3:04:31 PM7/31/08
to Google App Engine
So I've waited a few days for DNS A records for my domain bikezen.net
to propigate. Now I get a new error, when I try to add the app to just
http://bikezen.net I get "Invalid Domain" instead of silent failure, I
don't know if this is a step forward or a step back.
Per http://www.google.com/support/a/bin/answer.py?answer=91080&hl=en I
set the A names correctly, dig output confirms:
;; QUESTION SECTION:
;bikezen.net. IN A
;; ANSWER SECTION:
bikezen.net. 1759 IN A 216.239.38.21
bikezen.net. 1759 IN A 216.239.32.21
bikezen.net. 1759 IN A 216.239.34.21
bikezen.net. 1759 IN A 216.239.36.21
I don't know if this is something specific to domains purchased
through google or what, I have a similar setup working fine on a
domain I purchased from another seller. The other domain is hosted on
dreamhost and I used their automatic DNS configuration, the odd thing
is that the A records listed for the domain differ from the one
googles documentation list as linked aboved. Since this is obviously
failing I think I'm going to try those next:
;; QUESTION SECTION:
;notevenanything.com. IN A
;; ANSWER SECTION:
notevenanything.com. 6443 IN A 72.14.207.121
notevenanything.com. 6443 IN A 64.233.179.121
notevenanything.com. 6443 IN A 66.249.81.121
On Jul 30, 11:30 am, WallyDD <shaneb...@gmail.com> wrote:
> Combining dns with Google Apps isn't the most fun. Even if it's right
> you have to wait 24/48 hours to convince yourself. And sometimes it
> still fails to work, so you have to do it all again.
>
> From memory;
> 1. I created temp.domain.com in google apps.
> 2. Added domain.com to the app/domain
> 3. Addedwww.domain.comto the app/domain
to propigate. Now I get a new error, when I try to add the app to just
http://bikezen.net I get "Invalid Domain" instead of silent failure, I
don't know if this is a step forward or a step back.
Per http://www.google.com/support/a/bin/answer.py?answer=91080&hl=en I
set the A names correctly, dig output confirms:
;; QUESTION SECTION:
;bikezen.net. IN A
;; ANSWER SECTION:
bikezen.net. 1759 IN A 216.239.38.21
bikezen.net. 1759 IN A 216.239.32.21
bikezen.net. 1759 IN A 216.239.34.21
bikezen.net. 1759 IN A 216.239.36.21
I don't know if this is something specific to domains purchased
through google or what, I have a similar setup working fine on a
domain I purchased from another seller. The other domain is hosted on
dreamhost and I used their automatic DNS configuration, the odd thing
is that the A records listed for the domain differ from the one
googles documentation list as linked aboved. Since this is obviously
failing I think I'm going to try those next:
;; QUESTION SECTION:
;notevenanything.com. IN A
;; ANSWER SECTION:
notevenanything.com. 6443 IN A 72.14.207.121
notevenanything.com. 6443 IN A 64.233.179.121
notevenanything.com. 6443 IN A 66.249.81.121
On Jul 30, 11:30 am, WallyDD <shaneb...@gmail.com> wrote:
> Combining dns with Google Apps isn't the most fun. Even if it's right
> you have to wait 24/48 hours to convince yourself. And sometimes it
> still fails to work, so you have to do it all again.
>
> From memory;
> 1. I created temp.domain.com in google apps.
> 2. Added domain.com to the app/domain
> 3. Pointed the A records to googles numbers. (in godaddy)
> 4. Linked the www record to ghs.google.com (in godaddy)
> 5. Waited 24/48 hours found it didn't work.
> 6. Removed thewww.domain.comlink from the app/domain, then added it
> 4. Linked the www record to ghs.google.com (in godaddy)
> 5. Waited 24/48 hours found it didn't work.
> again.
>
> Hope this helps.
>
> On Jul 30, 11:05 pm, Jonathan Feinberg <e.e.c...@gmail.com> wrote:
>
> > I have created the mywordle GAE app.
>
> > I have created the mywordle google apps domain, in order to point
> > mywordle.net atthe GAE app.
>
> > I bought the mywordle.net domain through Google Apps, and the godaddy
> > cnames and anames are
> > all configured correctly by google, such that the mywordle.net name
> > and its various cnames all work as expected.
>
> > I can create the GAE app as a service in google apps, with a dumb
> > default URL of mywordle.mywordle.net.
>
> > When I attempt to add either ofwww.mywordle.netormywordle.net, the
>
> Hope this helps.
>
> On Jul 30, 11:05 pm, Jonathan Feinberg <e.e.c...@gmail.com> wrote:
>
> > I have created the mywordle GAE app.
>
> > I have created the mywordle google apps domain, in order to point
> > mywordle.net atthe GAE app.
>
> > I bought the mywordle.net domain through Google Apps, and the godaddy
> > cnames and anames are
> > all configured correctly by google, such that the mywordle.net name
> > and its various cnames all work as expected.
>
> > I can create the GAE app as a service in google apps, with a dumb
> > default URL of mywordle.mywordle.net.
>
Eric Gillingham
Aug 7, 2008, 3:15:51 PM8/7/08
to Google App Engine
Well neither approach seems to work, both using the A entries provided
by google after it tells my the domain is invalid, or using the
entries that work for my other app and other domain. Is there any way
to actually contact google about this? It's quite frustrating when I
was expecting hey if I buy the domain through google it should make
life easier, instead it's making it a lot more difficult.
On Jul 31, 12:04 pm, Eric Gillingham <E...@notevenanything.com> wrote:
> So I've waited a few days for DNS A records for my domain bikezen.net
> to propigate. Now I get a new error, when I try to add the app to justhttp://bikezen.netI get "Invalid Domain" instead of silent failure, I
> > 3. Addedwww.domain.comtothe app/domain
by google after it tells my the domain is invalid, or using the
entries that work for my other app and other domain. Is there any way
to actually contact google about this? It's quite frustrating when I
was expecting hey if I buy the domain through google it should make
life easier, instead it's making it a lot more difficult.
On Jul 31, 12:04 pm, Eric Gillingham <E...@notevenanything.com> wrote:
> So I've waited a few days for DNS A records for my domain bikezen.net
> > 3. Pointed the A records to googles numbers. (in godaddy)
> > 4. Linked the www record to ghs.google.com (in godaddy)
> > 5. Waited 24/48 hours found it didn't work.
> > 6. Removed thewww.domain.comlinkfrom the app/domain, then added it
> > 4. Linked the www record to ghs.google.com (in godaddy)
> > 5. Waited 24/48 hours found it didn't work.
ia
Aug 7, 2008, 3:28:38 PM8/7/08
to Google App Engine
I'm having the same issue as Jonathan, with silent failure for both
www and the naked domain, even with a placeholder subdomain in place.
Has anyone managed get a resolution on this?
www and the naked domain, even with a placeholder subdomain in place.
Has anyone managed get a resolution on this?
Leo
Aug 13, 2008, 10:08:42 PM8/13/08
to Google App Engine
I'm having the same problem.
I have the A records on raeleo.com set up correctly and I get "invalid
domain" when I try to add my naked domain, raeleo.com, to the list of
URLs which point to my app engine app. The URL which succeeded is
raechelleleo.raeleo.com An oddity is that a visiting raeleo.com
results in a redirect from the google appengine IPs I set as A records
on this domain. The redirect is to a host I had setup previously in
google apps pointing to the site creation tool: pages.raeleo.com.
That request fails because I don't have DNS setup for
pages.raeleo.com.
I too have another domain, squidpress.com, setup similarly in DNS and
for that one I can add the naked domain to the list of URLs that point
to a different app engine app in a different google apps account.
I've tried deleting and re adding the urls on the app engine config in
the google apps dashboard a few different ways to see if this would
reset it. I even removed the app engine app from my active services.
No luck. I still can't add the naked domain to my URL list.
Google, what is the status of this problem? Let us know if we're
doing something wrong or you're working on a bug.
Sincerely,
Leo, A person who likes the simplicity you're trying to offer us.
On Aug 7, 3:28 pm, ia <i.an...@gmail.com> wrote:
> I'm having the same issue as Jonathan, with silent failure for both
> www and thenakeddomain, even with a placeholder subdomain in place.
I have the A records on raeleo.com set up correctly and I get "invalid
domain" when I try to add my naked domain, raeleo.com, to the list of
URLs which point to my app engine app. The URL which succeeded is
raechelleleo.raeleo.com An oddity is that a visiting raeleo.com
results in a redirect from the google appengine IPs I set as A records
on this domain. The redirect is to a host I had setup previously in
google apps pointing to the site creation tool: pages.raeleo.com.
That request fails because I don't have DNS setup for
pages.raeleo.com.
I too have another domain, squidpress.com, setup similarly in DNS and
for that one I can add the naked domain to the list of URLs that point
to a different app engine app in a different google apps account.
I've tried deleting and re adding the urls on the app engine config in
the google apps dashboard a few different ways to see if this would
reset it. I even removed the app engine app from my active services.
No luck. I still can't add the naked domain to my URL list.
Google, what is the status of this problem? Let us know if we're
doing something wrong or you're working on a bug.
Sincerely,
Leo, A person who likes the simplicity you're trying to offer us.
On Aug 7, 3:28 pm, ia <i.an...@gmail.com> wrote:
> I'm having the same issue as Jonathan, with silent failure for both
Leo
Aug 14, 2008, 10:06:25 AM8/14/08
to Google App Engine
This morning I dug further since I didn't stir any to answer this
question last night and I found the answer for me at least. Here it
is:
You get invalid domain when adding the naked domain when your version
of google apps ("Manage this domain"->"Domain settings"->"Control
panel"->"Next generation" ) set to "Next generation" instead of
"Current version" ("Manage this domain"->"Domain settings"->"Control
panel"->"Current version"). I switched my google apps control panel
version to "Current version" and promptly visited the app engine app
URL management area and SUCCESSFULLY added the naked domain
raeleo.com!
I found the answer at: http://movetogae.blogspot.com/2008/08/setting-up-dns.html
Not in the main post, but in a follow up comment. Thank you Akash
Xavier.
In case you are wondering, yes the domain which allowed me to add the
naked domain all along had the default Control panel version of
"Current version" I hadn't fooled around with that one.
On Aug 13, 10:08 pm, Leo <l...@raeleo.com> wrote:
> I'm having the same problem.
>
> I have the A records on raeleo.com set up correctly and I get "invalid
> domain" when I try to add my naked domain, raeleo.com, to the list of
> URLs which point to my app engine app. The URL which succeeded is
> raechelleleo.raeleo.com An oddity is that a visiting raeleo.com
> results in a redirect from the google appengine IPs I set as A records
> on this domain. The redirect is to a host I had setup previously in
> google apps pointing to the site creation tool: pages.raeleo.com.
> That request fails because I don't have DNS setup for
> pages.raeleo.com.
>
> I too have another domain, squidpress.com, setup similarly in DNS and
> for that one I can add the naked domain to the list of URLs that point
> to a different app engine app in a different google apps account.
>
> I've tried deleting and re adding the urls on the app engine config in
> the google apps dashboard a few different ways to see if this would
> reset it. I even removed the app engine app from my active services.
> No luck. I still can't add the naked domain to my URL list.
>
> Google, what is the status of this problem? Let us know if we're
> doing something wrong or you're working on a bug.
>
> Sincerely,Leo, A person who likes the simplicity you're trying to offer us.
question last night and I found the answer for me at least. Here it
is:
You get invalid domain when adding the naked domain when your version
of google apps ("Manage this domain"->"Domain settings"->"Control
panel"->"Next generation" ) set to "Next generation" instead of
"Current version" ("Manage this domain"->"Domain settings"->"Control
panel"->"Current version"). I switched my google apps control panel
version to "Current version" and promptly visited the app engine app
URL management area and SUCCESSFULLY added the naked domain
raeleo.com!
I found the answer at: http://movetogae.blogspot.com/2008/08/setting-up-dns.html
Not in the main post, but in a follow up comment. Thank you Akash
Xavier.
In case you are wondering, yes the domain which allowed me to add the
naked domain all along had the default Control panel version of
"Current version" I hadn't fooled around with that one.
On Aug 13, 10:08 pm, Leo <l...@raeleo.com> wrote:
> I'm having the same problem.
>
> I have the A records on raeleo.com set up correctly and I get "invalid
> domain" when I try to add my naked domain, raeleo.com, to the list of
> URLs which point to my app engine app. The URL which succeeded is
> raechelleleo.raeleo.com An oddity is that a visiting raeleo.com
> results in a redirect from the google appengine IPs I set as A records
> on this domain. The redirect is to a host I had setup previously in
> google apps pointing to the site creation tool: pages.raeleo.com.
> That request fails because I don't have DNS setup for
> pages.raeleo.com.
>
> I too have another domain, squidpress.com, setup similarly in DNS and
> for that one I can add the naked domain to the list of URLs that point
> to a different app engine app in a different google apps account.
>
> I've tried deleting and re adding the urls on the app engine config in
> the google apps dashboard a few different ways to see if this would
> reset it. I even removed the app engine app from my active services.
> No luck. I still can't add the naked domain to my URL list.
>
> Google, what is the status of this problem? Let us know if we're
> doing something wrong or you're working on a bug.
>
julian.amaya
Aug 15, 2008, 4:38:49 PM8/15/08
to Google App Engine
it did it for me :) thank you so much!!!
> > That request fails because I don't haveDNSsetup for
Eric Gillingham
Aug 17, 2008, 2:27:11 PM8/17/08
to Google App Engine
Huge thanks for this, who knew it would be such a simple fix.
ulfur
Aug 21, 2008, 8:37:09 AM8/21/08
to Google App Engine
Thank you so much...
This issue had been bugging me for days.
I hope the fix this issue soon as the plan for my app is to allow end-
users to add it as their main page handler so it would be a drag if an
issue like this were to complicate the matter.
This issue had been bugging me for days.
I hope the fix this issue soon as the plan for my app is to allow end-
users to add it as their main page handler so it would be a drag if an
issue like this were to complicate the matter.
Dennis
Sep 8, 2008, 6:49:14 AM9/8/08
to Google App Engine
Worked for me, also!! But,....
I'm a bit concerned:
this workaround will work while the current version of the control
panel is available.
When google apps upgrades it, the workaround will stop working.
I tried the google suggestion of forwarding my domain (naked or not)
to www.my_domain.com ( http://www.google.com/support/a/bin/answer.py?answer=91080&hl=en
) but it did not allow my naked domain to work (got a 404 error but I
did not wait for hours or days to see if that suggestion would work
after some time passes).
Just wondering if anyone has gotten naked domains to work using the
google suggested way...
> > > Has anyone managed get a resolution on this?- Hide quoted text -
>
> - Show quoted text -
I'm a bit concerned:
this workaround will work while the current version of the control
panel is available.
When google apps upgrades it, the workaround will stop working.
I tried the google suggestion of forwarding my domain (naked or not)
to www.my_domain.com ( http://www.google.com/support/a/bin/answer.py?answer=91080&hl=en
) but it did not allow my naked domain to work (got a 404 error but I
did not wait for hours or days to see if that suggestion would work
after some time passes).
Just wondering if anyone has gotten naked domains to work using the
google suggested way...
>
> - Show quoted text -
Paul Kinlan
Sep 8, 2008, 7:30:45 AM9/8/08
to google-a...@googlegroups.com
Yeah I had to do this one as well.
I don't think Google solution is a long term viable solution for the majority of users. For instance I can't configure my host to move eweri.com to www.eweri.com.
What is the reason why Google changed this?
Paul.
I don't think Google solution is a long term viable solution for the majority of users. For instance I can't configure my host to move eweri.com to www.eweri.com.
What is the reason why Google changed this?
Paul.
2008/9/8 Dennis <denni...@gmail.com>
Dennis
Oct 9, 2008, 11:02:55 AM10/9/08
to Google App Engine
I created Issue 777 for naked domain support:
http://code.google.com/p/googleappengine/issues/detail?id=777
On Sep 8, 7:30 pm, "Paul Kinlan" <paul.kin...@gmail.com> wrote:
> Yeah I had to do this one as well.
>
> I don't think Google solution is a long term viable solution for the
> majority of users. For instance I can't configure my host to move eweri.comtowww.eweri.com.
>
> What is the reason why Google changed this?
>
> Paul.
>
> 2008/9/8 Dennis <dennisf...@gmail.com>
> > > - Show quoted text -- Hide quoted text -
http://code.google.com/p/googleappengine/issues/detail?id=777
On Sep 8, 7:30 pm, "Paul Kinlan" <paul.kin...@gmail.com> wrote:
> Yeah I had to do this one as well.
>
> I don't think Google solution is a long term viable solution for the
> majority of users. For instance I can't configure my host to move eweri.comtowww.eweri.com.
>
> What is the reason why Google changed this?
>
> Paul.
>
>
>
>
>
>
> > Worked for me, also!! But,....
>
> > I'm a bit concerned:
> > this workaround will work while the current version of the control
> > panel is available.
> > When google apps upgrades it, the workaround will stop working.
>
> > I tried the google suggestion of forwarding my domain (naked or not)
> > towww.my_domain.com (
>
>
>
>
> > Worked for me, also!! But,....
>
> > I'm a bit concerned:
> > this workaround will work while the current version of the control
> > panel is available.
> > When google apps upgrades it, the workaround will stop working.
>
> > I tried the google suggestion of forwarding my domain (naked or not)
Reply all
Reply to author
Forward
0 new messages