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

Satisfied

Prashanth T. · Revisado há over 1 year

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á over 1 year

Vova H. · Revisado há over 1 year

Marco H. · Revisado há over 1 year

Rohit M. · Revisado há over 1 year

Andrew F. · Revisado há over 1 year

Souvik B. · Revisado há over 1 year

Carlos C. · Revisado há over 1 year

PATRYK K. · Revisado há over 1 year

Pawar s. · Revisado há over 1 year

Bill T. · Revisado há over 1 year

Haje K. · Revisado há over 1 year

Valdomiro J. · Revisado há over 1 year

Devin B. · Revisado há over 1 year

steven d. · Revisado há over 1 year

good

Muhammad Azym O. · Revisado há over 1 year

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

Noah D. · Revisado há over 1 year

Alaa A. · Revisado há over 1 year

MAHESH V. · Revisado há over 1 year

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á over 1 year

PRINCE M. · Revisado há over 1 year

Manuel L. · Revisado há over 1 year

Michael W. · Revisado há over 1 year

Forbes G. · Revisado há over 1 year

heshan j. · Revisado há over 1 year