Cloud DNS - Traffic Steering using Geolocation Policy avis

Yacine B. · Examiné il y a 11 mois

Satisfied

Prashanth T. · Examiné il y a 11 mois

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. · Examiné il y a 11 mois

Vova H. · Examiné il y a 11 mois

Marco H. · Examiné il y a 11 mois

Rohit M. · Examiné il y a 11 mois

Andrew F. · Examiné il y a 11 mois

Souvik B. · Examiné il y a 11 mois

Carlos C. · Examiné il y a 11 mois

PATRYK K. · Examiné il y a 11 mois

Pawar s. · Examiné il y a 11 mois

Bill T. · Examiné il y a 11 mois

Haje K. · Examiné il y a 11 mois

Valdomiro J. · Examiné il y a 11 mois

Devin B. · Examiné il y a 11 mois

steven d. · Examiné il y a 11 mois

good

Muhammad Azym O. · Examiné il y a 11 mois

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

Noah D. · Examiné il y a 11 mois

Alaa A. · Examiné il y a 11 mois

MAHESH V. · Examiné il y a 11 mois

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. · Examiné il y a 11 mois

PRINCE M. · Examiné il y a 11 mois

Manuel L. · Examiné il y a 11 mois

Michael W. · Examiné il y a 11 mois

Forbes G. · Examiné il y a 11 mois