An IP block tells SolusVM which assigned addresses it may allocate to servers and which compute resources can use them. Enter only addresses you are authorized to use. Adding an arbitrary public subnet to the panel does not make the internet route it to your infrastructure.
IN THIS ARTICLE
Check access and requirements
Collect the allocation from the provider, including usable boundaries, prefix or netmask, gateway, routing mode and resolver policy. Identify addresses already used by infrastructure or other guests. Confirm each selected compute resource can reach this network.
01 Add an IP block in SolusVM 2
- Open Network > Add IP Block and give the allocation an identifiable name.
- For IPv4, enter the assigned usable range, gateway, netmask and intended DNS resolvers. Exclude reserved or previously assigned addresses instead of relying on chance to avoid collisions.
- Associate only compute resources attached to the correct routed or bridged network. Do not select all hosts merely because they appear in the list.
- For IPv6, use the dedicated IPv6-block workflow and the provider-approved allocation/subnet design. IPv6 allocation and neighbor discovery need their own validation.
- Save, then deploy one test server. Record its assigned address and confirm the panel has reduced the available pool correctly before allowing wider provisioning.
Does an available IPv6 pool replace an exhausted IPv4 pool?
Do not assume it does. A plan or provisioning workflow may still require IPv4. Test the intended address-family combination and replenish the required pool before accepting orders.
Confirm the expected result
Use the test guest console to check addresses and routes. Validate outbound connectivity, DNS resolution and a permitted inbound connection from another network. Check for duplicate-address reports and confirm that reverse DNS is handled separately through the responsible provider or configured DNS integration.
Resolve setup problems
If provisioning reports no suitable addresses, inspect block-to-compute associations and remaining capacity. If a guest boots without connectivity, compare actual guest configuration with the allocation and upstream routing. Do not reassign a live address or delete an occupied block to clear an error. Suspend new allocations while reconciling conflicting records.