Cloud DNS - Traffic Steering using Geolocation Policy Ulasan

Seseyon W. · Diulas sekitar 1 bulan lalu

Duke L. · Diulas sekitar 1 bulan lalu

Yacine B. · Diulas sekitar 1 bulan lalu

Satisfied

Prashanth T. · Diulas sekitar 1 bulan lalu

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. · Diulas sekitar 1 bulan lalu

Vova H. · Diulas sekitar 1 bulan lalu

Marco H. · Diulas sekitar 1 bulan lalu

Rohit M. · Diulas sekitar 1 bulan lalu

Andrew F. · Diulas sekitar 1 bulan lalu

Souvik B. · Diulas sekitar 1 bulan lalu

Carlos C. · Diulas sekitar 1 bulan lalu

PATRYK K. · Diulas sekitar 1 bulan lalu

shah s. · Diulas sekitar 1 bulan lalu

Bill T. · Diulas sekitar 1 bulan lalu

Haje K. · Diulas sekitar 1 bulan lalu

Valdomiro J. · Diulas sekitar 1 bulan lalu

Devin B. · Diulas sekitar 1 bulan lalu

steven d. · Diulas sekitar 1 bulan lalu

good

Muhammad Azym O. · Diulas sekitar 1 bulan lalu

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

Noah D. · Diulas sekitar 1 bulan lalu

Alaa A. · Diulas sekitar 1 bulan lalu

MAHESH V. · Diulas sekitar 1 bulan lalu

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. · Diulas sekitar 1 bulan lalu

PRINCE M. · Diulas sekitar 1 bulan lalu

Manuel L. · Diulas sekitar 1 bulan lalu