在欧洲地区创建了GCE，但在美国显示了IP地址 [英] Created GCE in europe region but IP address shows its in US

问题描述

我创建了一个位于伦敦地区的实例

I have created an instance based in London region

由于来自客户的严格指导，我们必须确保在表明该应用程序位于欧盟以外的地方不存在任何痕迹.

Due to strict guidelines from client we have to make sure there should be no trace where it shows that the app is hosted outside EU.

甚至不在这里:

如果没有解决方案，我们将长期使用google服务，那么除了迁移到AWS之外，我们别无选择.

We are using google services from a long if we dont get a solution then we will have no other choice left except to move to AWS.

因为在AWS中，我们有一个RDS实例，该实例位于伦敦地区，所以当我们进行ip地址查找时，它会显示预期的结果.

Because in AWS we have a RDS instance which is based in London region and when we are doing the ip address lookup its showing the expected result.

>有什么方法可以使它指向仅欧洲区域而不是指向欧洲区域 包括美国在内的任何其他地区.

> Is there any way we can make it to point to only Europe region and not any other region including US.

我们已经将我们的应用程序部署到GAE实例中，但是由于它不提供对IP地址的任何更改.我试图为GCE寻找解决方案，但这也不能解决我们的问题.

We already have our application deployed into GAE instance but since it does not offer any changes into the ip address. I tried to look for a solution into the GCE but this also does not solve our issue.

谢谢.

更新OP

仅作记录.我们在支持门户网站上发布了一个问题， 甚至购买了金牌支持包来解决它.但是它变成了 指出这是无法实现的. 他们不由自主地获得跟踪路线以显示实际区域 对于相应实例所在的静态ip.我们最终>从GCP迁移到Azure平台.

Just for the records. We posted an issue on the support portal and even bought gold support package to get it resolved. But it turned out that it cant be achieved. They cant help out in getting the trace-route to show the actual region for static ip where the respective instance is located. And we ended up > migrating to Azure platform from GCP.

我会保持开放状态，也许GCP会在将来针对此问题提出解决方案.

I will keep it open, may be GCP will come up with a solution in future for this issue.

推荐答案

Google向GCP用户提供的所有IP地址均已通过 ARIN (换句话说，是 SWIP 到是加利福尼亚州的山景城).因此，即使实际服务器位于其他地方，所有IP地址的地理位置查找都将解析为美国.除此之外，在GCP中，将一个IP块从一个位置重新映射到另一个位置并不罕见，尤其是考虑到GCP的IP地址具有弹性以及它们被回收或再利用的方式.

All the IP addresses Google provides to GCP user are registered with ARIN under the Google HQ in Mountain View, California (in other words SWIP to be Mountain View, CA). So, all geolocations lookup of the IP addresses will resolve to the United States even though the actual server is located somewhere else. In addition to that, in GCP, it's not uncommon to remap a block of IPs from one location to another, especially given the elasticity of IP addresses for the GCP and they way they are recycled or reused.

但是，取决于您使用的是哪种工具或网站来获取地理位置信息，信息可能因其可能正在使用其他数据库而无法更新或没有正确信息的事实而有所不同.关于IP的地理位置.

However, depending on which tool or website you are are using to get geolocation information the information may vary just because of the fact that they might be using a different database, which may not be updated or doesn’t have the right information regarding the geolocation of the IP.

您可以从ARIN(SEARCH WhoisRWS)获得此网站/工具，以获得更准确的答案，因为美国互联网号码注册机构(ARIN)是加拿大，美国和许多地区的地区互联网注册机构(RIR)加勒比海和北大西洋群岛.更多信息将提供更可靠的信息.

You could you this website/ tool from ARIN (SEARCH WhoisRWS) to get a more accurate answer as, the American Registry for Internet Numbers (ARIN) is the Regional Internet Registry (RIR) for Canada, the United States, and many Caribbean and North Atlantic islands. Which is more will provide more reliable information.

可能的解决方法是，您可以在具有用于EU的Geo本地IP地址的计算机上设置反向代理，并将请求从那里转发到您的Google Cloud Platform(GCP)VM实例.例如，在 CloudSigma 中启动nginx，然后将DNS指向该位置.

Possible workarounds, you could set up a reverse proxy on a machine that has a Geo local IP address for EU and forwards requests from there to your Google Cloud Platform (GCP) VM instance. For example, spin up nginx in CloudSigma and point the DNS at that.

这篇关于在欧洲地区创建了GCE，但在美国显示了IP地址的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！