Cloud DNS: Traffic Steering using Geolocation Policy Reviews
Loading...
No results found.

    Cloud DNS: Traffic Steering using Geolocation Policy Reviews

    3776 reviews

    Ankit . · Reviewed over 2 years ago

    Vishnu Vardhan M. · Reviewed over 2 years ago

    gaurav r. · Reviewed over 2 years ago

    vanam p. · Reviewed over 2 years ago

    Shahwaz A. · Reviewed over 2 years ago

    GEETIKA B. · Reviewed over 2 years ago

    RAHIL A. · Reviewed over 2 years ago

    Yashwanth N. · Reviewed over 2 years ago

    Tadi S. · Reviewed over 2 years ago

    Padala Kiran K. · Reviewed over 2 years ago

    jagadeesh v. · Reviewed over 2 years ago

    sasivenkatavamsi e. · Reviewed over 2 years ago

    Mohd H. · Reviewed over 2 years ago

    Venkata sai P. · Reviewed over 2 years ago

    Siva D. · Reviewed over 2 years ago

    Adarsh K. · Reviewed over 2 years ago

    Yeashwant B. · Reviewed over 2 years ago

    Harneet K. · Reviewed over 2 years ago

    Pradeep K. · Reviewed over 2 years ago

    IAP connection does not work.

    Bauke d. · Reviewed over 2 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 over 2 years ago

    Chandra Mohan G. · Reviewed over 2 years ago

    Subhrajyoti D. · Reviewed over 2 years ago

    zones had insufficient resources

    Patrick G. · Reviewed over 2 years ago

    Deepshikha P. · Reviewed over 2 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.