Cloud DNS: Traffic Steering using Geolocation Policy Reviews

10455 reviews

Monisha N. · Reviewed almost 4 years ago

vedantari l. · Reviewed almost 4 years ago

Gourav s. · Reviewed almost 4 years ago

Eshant A. · Reviewed almost 4 years ago

Ankit . · Reviewed almost 4 years ago

Vishnu Vardhan M. · Reviewed almost 4 years ago

gaurav r. · Reviewed almost 4 years ago

vanam p. · Reviewed almost 4 years ago

Shahwaz A. · Reviewed almost 4 years ago

GEETIKA B. · Reviewed almost 4 years ago

RAHIL A. · Reviewed almost 4 years ago

Yashwanth N. · Reviewed almost 4 years ago

Tadi S. · Reviewed almost 4 years ago

Padala Kiran K. · Reviewed almost 4 years ago

jagadeesh v. · Reviewed almost 4 years ago

sasivenkatavamsi e. · Reviewed almost 4 years ago

Mohd H. · Reviewed almost 4 years ago

Venkata sai P. · Reviewed almost 4 years ago

Siva D. · Reviewed almost 4 years ago

Adarsh K. · Reviewed almost 4 years ago

Yeashwant B. · Reviewed almost 4 years ago

Harneet K. · Reviewed almost 4 years ago

Pradeep K. · Reviewed almost 4 years ago

IAP connection does not work.

Bauke d. · Reviewed almost 4 years ago

Good overview lab. Couple observations, issue, and comment. The biggest issue that I encountered in this lab is "ERROR: (gcloud.compute.instances.create) Could not fetch resource:" Specifically, I wasn't about to create the VM as instructed due this error for europe-wes2-a, asia-south1-a/b/c zones. So, I ended up create the client and server in europe-west2-b, and asia-south2-a. Grading is good enough to overlook these subtle disconnects. It will be even better if we can introduce some verification steps in this lab; either in cloud shell, cloud console, or even both. Lastly, for my lab, when trying to access the web server from the asia-south2-a zone, all the curl goes to us-east server. Since the us-east is much farther away from europe-west from the distance perspective of asia-southe2-a, this output kind of surprised me. Perhaps there is some behind the scene setting that may help in explaining it? Thanks. Regards, KC

Tgo168 C. · Reviewed almost 4 years ago

We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.