Hey Richard, I fully understand why it's not preferable to have to set up a proxy, but such is the necessity of living within a network with malicious mis-routing. At any rate, that's what I've read elsewhere on the net is what someone might do if faced with the situation of such actually occurring. Anything you implement would be up to you. I wish you the best of luck, overall.
As to Custom Domain SSL in the Developers Console, I think there's another thread <https://groups.google.com/forum/#!topic/google-appengine/hplw7Y7hZPM> on the front page of the group right now which address this issue, so it would be best to check there. Thanks for your reply, Nick On Saturday, September 5, 2015 at 3:08:56 AM UTC-4, Richard Cheesmar wrote: > > Hi, Nick, > > The point is access for the public. People are not going to use VPS etc > for access to a real estate website. As I said previously outside of Turkey > you can access both naked and www domains, but inside just the www. This > isn't a real game changer, it's just a nuisance. I personally hate the www > prefix. Anyway, I'm not focusing on this at the moment, bugs to fix...will > take another look before properly launching. > > By the way any news on the SSL in the developers console yet? It's > September already... > > Regards > > Richard > > On Fri, Sep 4, 2015 at 11:56 PM, Nick (Cloud Platform Support) < > pay...@google.com> wrote: > >> Hey Richard, >> >> Thanks for the detailed report of your network. I'm currently re-reading >> your post to see if I have anything else to recommend. Not being a lawyer, >> I can't comment on the legal implications of, for example, using a VPS or >> virtual IP to circumvent bad routing or blockages. Let me know if you have >> any specific questions I might be able to help answer. >> >> Regards, >> >> Nick >> >> >> On Tuesday, September 1, 2015 at 3:23:02 AM UTC-4, Richard Cheesmar wrote: >>> >>> Forgot to mention, the naked domain doesn't work on a phone under 3g >>> either >>> >>> On Tue, Sep 1, 2015 at 10:18 AM, Richard Cheesmar <chezand...@gmail.com> >>> wrote: >>> >>>> Excuse the typos1 >>>> >>>> On Tue, Sep 1, 2015 at 10:16 AM, Richard Cheesmar <chezand...@gmail.com >>>> > wrote: >>>> >>>>> Hi, Nick, >>>>> >>>>> Although, I cannot be positive without access to relevant servers, I'm >>>>> afraid it is a block. I think that your Public DNS servers along with >>>>> others like OpendDNS are spoofed by Turk Telecom servers pretending to >>>>> be >>>>> yours. Not only that, I think they have put in place IP blacklists on >>>>> certain blocks of IPs for Google and others, so it doesn't matter if you >>>>> do >>>>> not use their DNS IPs. This has been going on sometime. >>>>> >>>>> I have used a Cname record for the www domain and that works just >>>>> fine, however, the naked domain is on a A name record and this originally >>>>> had you gae ip addresses in, 4 records in all. I then forwarded naked to >>>>> www, but it didn't work. I then deleted the A name records and replaced >>>>> with a non google ip address provided by whois.com. Still doesn't >>>>> work inside Turkey so I am thinking that maybe they have noted the naked >>>>> domain and prevent that, but maybe that is me beign paranoid. Either way >>>>> it >>>>> works fine outside Turkey, just not inside. >>>>> >>>>> I have performed a traceroute for this and it hops 9 steps to a >>>>> turktelecom.com server in Ankara and then becomes anonymous. However, >>>>> if you run a traceroute from an online source it actually gets to the >>>>> destination. Pining simply return request timeouts here, however, the >>>>> whois.com support sent me screen shots of it pining successfully for >>>>> them. >>>>> >>>>> However, interestingly it won't ping from here: >>>>> http://tools.pingdom.com/ping/?target=emlakair.com&o=2&save=true , >>>>> not for me anyway, but you can see the forwarding working and perform a >>>>> traceroute. >>>>> >>>>> The www domain on the Cname record works fine and that is pointing to >>>>> ghs.googlehosted.com. In the beginning I had the naked domain working >>>>> within a Cname record also, but had to remove it as it was conflciting >>>>> with >>>>> the MX records for the mail server who rely on the naked domain to serve >>>>> me >>>>> mail. Cname record is taking priority so the MX records were not fired up. >>>>> >>>>> Anyway, I'm not sure what more I can do about this at the moment. I'm >>>>> still in Beta so will try to sort out before launching...properly >>>>> >>>>> >>>>> On Tue, Sep 1, 2015 at 1:51 AM, Nick (Cloud Platform Support) < >>>>> pay...@google.com> wrote: >>>>> >>>>>> Hi Richard, >>>>>> >>>>>> If you run a whois lookup on those addresses, you'll see they belong >>>>>> to Google. I'm not a lawyer and not an expert on international >>>>>> relations, >>>>>> but it's possible there is a block as you say. This might be caused from >>>>>> within your local network, a proxy or bridge used by an ISP, etc. Could >>>>>> you >>>>>> try to run a traceroute <https://en.wikipedia.org/wiki/Traceroute> >>>>>> or mtr <https://en.wikipedia.org/wiki/MTR_(software)> from your >>>>>> location to see exactly what happens to your packets? >>>>>> >>>>>> These are my first thoughts on debugging your connection problem. >>>>>> >>>>>> Best wishes, >>>>>> >>>>>> Nick >>>>>> >>>>>> On Sunday, August 30, 2015 at 6:06:46 AM UTC-4, Richard Cheesmar >>>>>> wrote: >>>>>>> >>>>>>> Ok, what is apparent is that the following set of ip addresses are >>>>>>> being blocked in Turkey: >>>>>>> >>>>>>> 216.239.36.21 >>>>>>> 216.239.32.21 >>>>>>> 216.239.38.21 >>>>>>> 216.239.34.21 >>>>>>> >>>>>>> Therefore, no naked custom domains with A records and these >>>>>>> addresses are going to work in Turkey >>>>>>> >>>>>>> What is the solution: Signing Up to Google Apps and a work account >>>>>>> so that I can redirect via the google admin console or do Google have >>>>>>> another set of ip addresses for app engine projects that are not likely >>>>>>> blocked? >>>>>>> >>>>>>> Anyone got any alternatives? >>>>>>> >>>>>>> >>>>>>> On Saturday, August 29, 2015 at 10:01:54 AM UTC+3, Richard Cheesmar >>>>>>> wrote: >>>>>>>> >>>>>>>> I have added two custom domains to Google Developers Console for a >>>>>>>> Google App Project. >>>>>>>> >>>>>>>> >>>>>>>> One, a naked domain with A and AAA records set on the third party >>>>>>>> DNS manager as specified by Google. Two, a www domain with a Cname >>>>>>>> record >>>>>>>> set on the third party DNS manager, as specified by Google. >>>>>>>> >>>>>>>> >>>>>>>> The www is serving, but the naked domain is not! The A records ip >>>>>>>> addresses timeout on my local machine but I get results when using >>>>>>>> http://tools.pingdom.com/ping/ >>>>>>>> >>>>>>>> Obviously you can use more than one custom domain but is there >>>>>>>> something I'm missing here? >>>>>>>> >>>>>>> -- >>>>>> You received this message because you are subscribed to a topic in >>>>>> the Google Groups "Google App Engine" group. >>>>>> To unsubscribe from this topic, visit >>>>>> https://groups.google.com/d/topic/google-appengine/Me7Svp7kE88/unsubscribe >>>>>> . >>>>>> To unsubscribe from this group and all its topics, send an email to >>>>>> google-appengine+unsubscr...@googlegroups.com. >>>>>> To post to this group, send email to >>>>>> google-appengine@googlegroups.com. >>>>>> Visit this group at http://groups.google.com/group/google-appengine. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/google-appengine/5b54d03d-cdf8-4056-a409-19f26b91f168%40googlegroups.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/google-appengine/5b54d03d-cdf8-4056-a409-19f26b91f168%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>>> >>>> >>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Google App Engine" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/google-appengine/Me7Svp7kE88/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> google-appengine+unsubscr...@googlegroups.com. >> To post to this group, send email to google-appengine@googlegroups.com. >> Visit this group at http://groups.google.com/group/google-appengine. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/google-appengine/d357e888-e948-4481-91f0-710605bf838d%40googlegroups.com >> >> <https://groups.google.com/d/msgid/google-appengine/d357e888-e948-4481-91f0-710605bf838d%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/6da8a8af-5ab5-4f05-98d6-8e47c465f49b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
