Working with multiple VPC networks Reviews

non funziona

Andrea M. · Reviewed 12 months ago

Finlay P. · Reviewed 12 months ago

Arianit K. · Reviewed 12 months ago

kofi a. · Reviewed 12 months ago

Namit S. · Reviewed 12 months ago

Goravit B. · Reviewed 12 months ago

had to change disk type because of shortage in the designed zone

Tahar J. · Reviewed 12 months ago

Jano A. · Reviewed 12 months ago

Stefan G. · Reviewed 12 months ago

Mehmet Hikmet D. · Reviewed 12 months ago

the vm instance is frozen

Eoin M. · Reviewed 12 months ago

pretty satisfied

Mithuna P. · Reviewed 12 months ago

task 4 can never complete for the vm-appliance creation

Ka Wing T. · Reviewed 12 months ago

nicoleta i. · Reviewed 12 months ago

Nikita I. · Reviewed 12 months ago

Bhavani V. · Reviewed 12 months ago

Sabarinathan S. · Reviewed 12 months ago

FNU M. · Reviewed 12 months ago

Chun-Yi T. · Reviewed 12 months ago

This didn't work: You can ping privatenet-us-vm by its name because VPC networks have an internal DNS service that allows you to address instances by their DNS names instead of their internal IP addresses. When an internal DNS query is made with the instance hostname, it resolves to the primary interface (nic0) of the instance. Therefore, this only works for privatenet-us-vm in this case.

Elena K. · Reviewed 12 months ago

Grégory W. · Reviewed 12 months ago

Lisa A. · Reviewed 12 months ago

David F. · Reviewed 12 months ago

Esperanza R. · Reviewed 12 months ago

Marcelo S. · Reviewed 12 months ago