Cloud DNS Geolocation fallback

[abzkk]

Hi,

We're setting up a CNAME record in Cloud DNS that needs to utilize geolocation. In our case:

```

asia-east2 / china.oursite.com

everywhere else / oursite.com

```

However, this would require us to add entries for each region outside of `asia-east2` to ensure they're routed correctly. This is fine for a one-off, but isn't future proof if google adds future regions or changes the existing ones.

is there a way to add a catch-all geolocation item?

[Marvin_Lucero · Accepted solution]

Hi @abzkk ,

It seems that there is no direct way to add a catch-all geolocation item in Cloud DNS. However, there are some alternative solutions that you can consider.

One possible solution is to use a third-party DNS provider that supports geolocation with a catch-all option. For example, Cloudflare offers a feature called "Traffic Steering". Cloudflare's traffic steering feature can be used with Google Cloud by configuring Cloudflare as a DNS provider for your domain, and then using Cloudflare's traffic steering rules to route traffic based on various factors such as latency, geolocation, or load.

Another solution is to use a load balancer or reverse proxy with geolocation capabilities. For example, you can use Google Cloud Load Balancing or NGINX Plus  to route traffic based on the client's location. With this approach, you can define a default rule that routes all traffic to a specific IP address or hostname.

Let me know if this answers your question.