关于“Working with multiple VPC networks”的评价

Víctor Hugo P. · 已于 over 1 year前审核

Paul L. · 已于 over 1 year前审核

Chen F. · 已于 over 1 year前审核

non funziona

Andrea M. · 已于 over 1 year前审核

Finlay P. · 已于 over 1 year前审核

Arianit K. · 已于 over 1 year前审核

kofi a. · 已于 over 1 year前审核

Namit S. · 已于 over 1 year前审核

Goravit B. · 已于 over 1 year前审核

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

Tahar J. · 已于 over 1 year前审核

Jano A. · 已于 over 1 year前审核

Stefan G. · 已于 over 1 year前审核

Mehmet Hikmet D. · 已于 over 1 year前审核

the vm instance is frozen

Eoin M. · 已于 over 1 year前审核

pretty satisfied

Mithuna P. · 已于 over 1 year前审核

task 4 can never complete for the vm-appliance creation

Ka Wing T. · 已于 over 1 year前审核

nicoleta i. · 已于 over 1 year前审核

Nikita I. · 已于 over 1 year前审核

Bhavani V. · 已于 over 1 year前审核

Sabarinathan S. · 已于 over 1 year前审核

FNU M. · 已于 over 1 year前审核

Chun-Yi T. · 已于 over 1 year前审核

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. · 已于 over 1 year前审核

Grégory W. · 已于 over 1 year前审核

Lisa A. · 已于 over 1 year前审核