DNS settings for naked domain in non-US region.

70 views
Skip to first unread message

Dev Vercer

unread,
Aug 24, 2017, 10:31:26 PM8/24/17
to Google App Engine
Apologies for cross posing with stack overflow (no replies on post)

I have set up my site at a naked domain https://example.com using the recommend DNS Settingswhich uses A Records to declare the ip addresses of Google's hosting servers.

My site is in the new London region but the IP addresses point to the US.

My question is, are there other IP addresses I should use for non-US regions?

Is the only reason to not use a CNAME so that MX records will still work? (I do not need mail on this domain)

Can I use the CNAME ghs.googlehosted.com on the naked domain?

Yannick (Cloud Platform Support)

unread,
Aug 25, 2017, 12:01:38 PM8/25/17
to Google App Engine
Hello,

There should be no need to use other IPs as your application will still serve traffic from the region it was created in. Was that your concern?

I also believe this configuration allows for the use of subdomains for your App Engine services.

Dev Vercer

unread,
Aug 28, 2017, 4:00:14 AM8/28/17
to Google App Engine


On Saturday, August 26, 2017 at 2:01:38 AM UTC+10, Yannick (Cloud Platform Support) wrote:

There should be no need to use other IPs as your application will still serve traffic from the region it was created in. Was that your concern?

I am worried that requests from users in the UK will be routed through the US because the servers with these IP addresses are located there (according to several location services).

If this is not the case, how do these magical IP addresses work? ;)

 

I also believe this configuration allows for the use of subdomains for your App Engine services.

Subdomains are configured with a CNAME ghs.googlehosted.com so I assume this can return different IP addresses depending on where is is queried from. i.e. from London the DNS could return IP addresses for local servers.

Yannick (Cloud Platform Support)

unread,
Aug 28, 2017, 12:50:19 PM8/28/17
to Google App Engine
These magical IPs are possible thanks to Google's edge network. The edge network locations advertise themselves as a route to these IPs so a user's request will go straight into our network and reach the closest data center. This means the request will not need to traverse the internet to California and back to serve your users.

What results do you get when you try to ping or traceroute your application serving on the domain?
Reply all
Reply to author
Forward
0 new messages