Cloud DNS — direcionamento de tráfego usando política de geolocalização avaliações

Seseyon W. · Revisado há about 1 month

Duke L. · Revisado há about 1 month

Yacine B. · Revisado há about 1 month

Satisfied

Prashanth T. · Revisado há about 1 month

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. · Revisado há about 1 month

Vova H. · Revisado há about 1 month

Marco H. · Revisado há about 1 month

Rohit M. · Revisado há about 1 month

Andrew F. · Revisado há about 1 month

Souvik B. · Revisado há about 1 month

Carlos C. · Revisado há about 1 month

PATRYK K. · Revisado há about 1 month

shah s. · Revisado há about 1 month

Bill T. · Revisado há about 1 month

Haje K. · Revisado há about 1 month

Valdomiro J. · Revisado há about 1 month

Devin B. · Revisado há about 1 month

steven d. · Revisado há about 1 month

good

Muhammad Azym O. · Revisado há about 1 month

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

Noah D. · Revisado há about 1 month

Alaa A. · Revisado há about 1 month

MAHESH V. · Revisado há about 1 month

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. · Revisado há about 1 month

PRINCE M. · Revisado há about 1 month

Manuel L. · Revisado há about 1 month