VM networking
Each VM created in Compute Cloud has a network interface that belongs to the default subnet from Virtual Private Cloud. The interface is assigned an internal IP address from this subnet and an internal FQDN which allow communication between the VM and other Nebius AI resources you create. You can also enable a public IP address which can be used for communication between the VM and the Internet.
You can find out the IP addresses, FQDNs, and other information in the management console by going to the Network section on the virtual machine page. This data can be used to connect to the VM.
On VMs created from public Linux images, the IP address and hostname (FQDN) are not automatically written to the /etc/hosts
file. This may affect running the sudo
command.
You can attach a public address to or detach it from your VM at any time without stopping or shutting the VM.
Internal IP address
Each VM is assigned an internal IPv4 address on its creation. You can use this address to connect to other resources in Nebius AI (VMs, Managed Service for Kubernetes cluster nodes etc.).
The VM's internal IP address is selected randomly. You cannot change it.
Public IP address
You can enable a public IPv4 address for your VM to access it from the internet.
Public IP addresses assigned to VMs are dynamic. When the VM is stopped, the dynamic address is released, and the VM gets a new public IP address when started next time. When the VM is restarted, the address does not change. You can make the VM's dynamic address static. For more details, see Public IP addresses.
Public IP addresses belong to the Nebius AI address range. They are allocated randomly. You cannot select a specific address.
You are charged for using public IP addresses. For details about the charges, see the Public IP addresses section of the Virtual Private Cloud documentation.
The VM's public IP address is mapped to its internal IP address through NAT. This means all requests to the VM from an external IP address are sent to an internal IP address. For more information about NAT, see RFC 3022
Host name and internal FQDN
When creating a VM, it is assigned a host name and internal FQDN that can be used to access a certain VM from another VM within the same cloud network.
Once the VM is created, you cannot change its host name and internal FQDN.
The assigned FQDN depends on the specified host name (CreateInstanceSpec.hostname)
. The host name must be unique in your virtual network.
-
You cannot specify the
hostname
parameter in the management console for a new VM. Instead, the user-defined VM name is used:- If you leave the Name field blank when creating a VM, it will be assigned an internal FQDN in the
<VM ID>.auto.internal
format. - If you provide a VM name in the Name field, it will be assigned an internal FQDN in the
<VM name>.<region>.internal
format.
- If you leave the Name field blank when creating a VM, it will be assigned an internal FQDN in the
-
When using Nebius AI interfaces other than the management console, FQDNs are created as follows:
- If you do not specify any
hostname
, the VM will be assigned a unique FQDN in the<VM ID>.auto.internal
format. - If the
hostname
is specified and contains no periods (.
), it is treated as an FQDN prefix. The VM will be assigned an internal FQDN in the<hostname>.<region>.internal
format. - If the
hostname
is specified and contains a period (.
) in the middle or at the end, it is treated as an FQDN. The internal FQDN assigned to the VM is the same as thehostname
. FQDNs cannot start with a period (.
) or only contain periods (.
).
- If you do not specify any
Examples
Specified host name | VM FQDN |
---|---|
<not specified> |
<VM ID>.auto.internal |
breathtaking |
breathtaking.eu-north1.internal |
this-is-sparta |
this-is-sparta.eu-north1.internal |
hello.world or hello.world. |
hello.world |
breathtaking. |
breathtaking |
.why |
error (FQDN starts with ".") |
. |
error (FQDN contains dots "." only) |
MAC address
Once the network interface is connected to a VM, it will be assigned the device MAC address.
You can find out the MAC address from a VM or in the resource information using the Nebius AI API.