[google-appengine] Re: app engine hosted website - the domain is no longer parked by GoDaddy

2017-08-18 Thread Sumanta Bhowmik
Hi I am also facing the same issue even though I have removed all unwanted A/ records. There is record CNAME _domainconnect _domainconnect.gd.domaincontrol.comShould I remove it? Regards Sumanta On Wednesday, 24 February 2016 22:26:58 UTC+5:30, Zeehad (Cloud Platform Support) wrote: > >

[google-appengine] Re: app engine hosted website - the domain is no longer parked by GoDaddy

2016-02-29 Thread Ahmed Layouni
Can't really answer your question but in the same context, I reached out to Godaddy on the issue before posting here, and their answer was clear your cache, this is a cache issue. Not convincing at all, but since the problem was inconsistent, and I couldn't get them to reproduce it, I had to

[google-appengine] Re: app engine hosted website - the domain is no longer parked by GoDaddy

2016-02-28 Thread Mark Pickles
Just wanted to say thanks for this. Different context but this helped me immensely. Why does GoDaddy add these extra records? is there some purpose, or is it just obstructing users who want to host elsewhere? I'd be interested to know if anyone has any answers/opinions. -- You received

[google-appengine] Re: app engine hosted website - the domain is no longer parked by GoDaddy

2016-02-24 Thread Ahmed Layouni
You're right Zeehad! I had one extra A record in my GoDaddy console, and 2 extra subdomains (ftp and mail) pre-configured by GoDaddy that were pointing to a different CNAME. I removed them all, hopefully the problem won't occur again. Thanks a lot! -Ahmed On Wednesday, February 24, 2016 at

[google-appengine] Re: app engine hosted website - the domain is no longer parked by GoDaddy

2016-02-24 Thread 'Zeehad (Cloud Platform Support)' via Google App Engine
Hello Ahmed, There is a very strong chance that some of your DNS records are still pointing to GoDaddy's custom parked domain page that you may have had setup prior to completing the App Engine custom domain setup. Please log in to your domain's management console and make sure the DNS zone