Cloud DNS - Traffic Steering using Geolocation Policy Reviews

Seseyon W. · Reviewed about 1 month ago

Duke L. · Reviewed about 1 month ago

Yacine B. · Reviewed about 1 month ago

Satisfied

Prashanth T. · Reviewed about 1 month ago

Very cool lab, but I think WRR would have been even cooler, especially when pointing out the use cases for it after the user can see that resolved IP addresses from asia seem somewhat random

Denis K. · Reviewed about 1 month ago

Vova H. · Reviewed about 1 month ago

Marco H. · Reviewed about 1 month ago

Rohit M. · Reviewed about 1 month ago

Andrew F. · Reviewed about 1 month ago

Souvik B. · Reviewed about 1 month ago

Carlos C. · Reviewed about 1 month ago

PATRYK K. · Reviewed about 1 month ago

shah s. · Reviewed about 1 month ago

Bill T. · Reviewed about 1 month ago

Haje K. · Reviewed about 1 month ago

Valdomiro J. · Reviewed about 1 month ago

Devin B. · Reviewed about 1 month ago

steven d. · Reviewed about 1 month ago

good

Muhammad Azym O. · Reviewed about 1 month ago

Good practice setting up servers and clients with routing policies using CLI.

Noah D. · Reviewed about 1 month ago

Alaa A. · Reviewed about 1 month ago

MAHESH V. · Reviewed about 1 month ago

student-01-ba8bef0c2f07@us-client-vm:~$ for i in {1..10}; do echo $i; curl geo.example.com; sleep 6; done 1 curl: (6) Could not resolve host: geo.example.com 2 curl: (6) Could not resolve host: geo.example.com 3 curl: (6) Could not resolve host: geo.example.com 4 curl: (6) Could not resolve host: geo.example.com 5 curl: (6) Could not resolve host: geo.example.com 6 curl: (6) Could not resolve host: geo.example.com 7 curl: (6) Could not resolve host: geo.example.com 8 curl: (6) Could not resolve host: geo.example.com 9 curl: (6) Could not resolve host: geo.example.com 10 curl: (6) Could not resolve host: geo.example.com

Deepak S. · Reviewed about 1 month ago

PRINCE M. · Reviewed about 1 month ago

Manuel L. · Reviewed about 1 month ago