Every address a server gets comes from an IP block in Infrastructure › IP pools. A block belongs to one node; servers on that node are given its free addresses, lowest first. This page covers adding blocks, the block's page and its CSV import. How each block type reaches the network is on Routed IPv4 and IPv6, Bridged networking and VLANs.
IP pools are for administrators only.
Block types#
Add IP block asks for the kind first (IPv4, IPv6 or NAT) and shows only that kind's fields.
| Kind | Type | Use it for | Prefix |
|---|---|---|---|
| IPv4 | Gateway inside the block | A range on the node's link with the provider's gateway in it (a colocation /27, an OVHcloud vRack block) | /8 to /30 |
| IPv4 | Routed to this node's main IP | OVHcloud and Hetzner additional IPs and subnets, routed to the node's main address | /24 to /32 |
| IPv4 | Bridged: each address has its own MAC | OVHcloud virtual MACs, Hetzner separate MACs | /24 to /32 |
| IPv6 | On the node's link | The provider's /64 on the uplink segment; servers get single addresses | /32 to /120 |
| IPv6 | Routed to the node | A prefix routed to the node; servers can also get a subnet each | /32 to /120 |
| NAT | (one per node) | Servers without a public IPv4 address, reached through the node's ports | private, default 10.200.0.0/16 |
The Bridged type is offered once the database has the bridged networking migration. NAT networks are described on NAT and port forwards.
Blocks, nodes and locations#
A block is routed to exactly one node, chosen in the Node field when you add it. There is no block shared between nodes and no block assigned to a location. Locations use blocks indirectly: when a server is placed in a location, a node without enough free IPv4 addresses for it is passed over, and System › Placement log records it as "without enough free IPv4".
An address can be in only one block. Public addresses (IPv4 and IPv6) are unique panel-wide; NAT addresses are private to their node, so every node may use the same NAT network.
The node's own address is created Reserved when it lies in a block's range, and stays reserved.
Add an IPv4 block#
- Go to Infrastructure › IP pools › Add IP block.
- Choose IPv4.
- Under Settings, choose the Node and give a Name (up to 60 characters).
- Under Network, choose the Type and fill in its fields (below).
- Under DNS resolvers, enter one to four IPv4 resolvers, or use the Fill in: buttons (Google, Cloudflare, Quad9, OpenDNS). Empty means
1.1.1.1and8.8.8.8. - Under Additional settings, choose a Reverse DNS account or Manual, and add a Note if you want one.
- Click Add IPv4 block.
Gateway inside the block asks for:
| Field | Example | Notes |
|---|---|---|
| Gateway | 198.51.100.1 |
Not the network or broadcast address. |
| Prefix | 24 |
8 to 30. A /31 or /32 is refused: "A single address has no gateway inside it: it is routed to the node's main IP." |
| First address, Last address | 198.51.100.10 to 198.51.100.19 |
The range servers are given; not the network or broadcast address; at most 1024 addresses per block. |
A node cannot have two blocks with the same gateway and prefix.
Routed and Bridged ask for:
| Field | Example | Notes |
|---|---|---|
| Network | 203.0.113.8/29, or 203.0.113.50 |
The first address of the network, or a single address (read as /32). |
| Gateway | 192.0.2.254 |
The provider's gateway the node itself uses, outside the block. Filled in from the node's default gateway as reported by its agent. |
| First address, Last address | optional | Every address of the block is usable, network and broadcast included, unless you narrow it here. |
| MACs | bridged only | OVHcloud virtual MAC, account … or Entered per address. See Bridged networking. |
An empty name becomes 203.0.113.8/29 (routed), 203.0.113.50 (single) or … (bridged). A routed block that overlaps the node's own uplink network is refused: add it as Gateway inside the block instead.
Add an IPv6 block#
- Go to Infrastructure › IP pools › Add IP block and choose IPv6.
- Choose the Node and a Name.
- Enter the Subnet as the provider gives it, for example
2001:db8:100:200::/64. - Optional: The node's gateway (from the provider):
::1is read as this block's::1; a full address or a link-localfe80::one is taken as it is. - Optional: First usable and Last usable. Empty: from
::100up in a large block (from::2in a block of 512 addresses or fewer). - Choose How it reaches the node: On the node's link or Routed to the node.
- Enter DNS servers (empty: Cloudflare and Google over IPv6) and click Add IPv6 block.
The network address, the block's ::1, the provider's gateway and the node's own address are never given to a server. Servers always use fe80::1 (the node, on their bridge) as their IPv6 gateway. A block is refused when the node cannot route IPv6 to servers; the reason is shown. See Routed IPv4 and IPv6.
IPv6 addresses are not listed in advance (a /64 is too large). An address becomes a row when a server gets it, when somebody reserves it, or when you generate it.
Generate addresses and subnets#
The IPv6 block's page has a Generate panel:
- Addresses: 1 to 1000, One after another from Start at (in full or as its end, such as
::1000) or At random in the range. - Subnets (routed blocks only): a Size per server from /64 to /124, 1 to 1000, never the block's first subnet.
Generated entries are free rows marked "generated". Servers are given the free generated entries of their size first; when none is left, the panel picks the next free one itself, and the page says which sizes are used up.
The block page#
Click a block in Infrastructure › IP pools to open it. The header shows the counts (Free, In use, Reserved, and In use elsewhere when the address check marked any) and the buttons Export CSV, Import CSV, Edit block and Delete block.
The Addresses list shows 100 rows a page with the filters All, Free, In use, Reserved (and In use elsewhere), and a Find an address search. Each row has its state, its MAC (the fixed MAC, else the server's), its reverse DNS name, and actions:
| Action | What it does |
|---|---|
| Reserve / Release | A reserved address is never given to a server. An address in use cannot be reserved. The note is optional. |
| Set fixed MAC / Clear MAC | See Fixed MACs. |
| Reverse name | Sets the PTR name; see Reverse DNS. |
| Check now / Recheck / Clear mark | The address check, on checked blocks. |
| History | The address's audit entries and the servers it was given to. |
Tick rows that no server uses to Reserve, Release or (generated IPv6 entries only) Delete several at once. Reserve an address above the list reserves one by typing it, useful for IPv6.
Fixed MACs#
A fixed MAC is for providers that accept an address only from a MAC they generate. A server whose main address has a fixed MAC gets that MAC on its network card when it is created.
- It can be set or cleared only while the address is free. An address in use keeps its MAC: Reconfigure network does not change a server's card.
- An address with a fixed MAC is never given as an additional address, because a server has one network card.
- A MAC must be unicast, not all zeros, and not used by another address or by any server's card.
- Routed blocks refuse fixed MACs ("its traffic leaves with the node's MAC"). Bridged blocks with OVHcloud virtual MAC refuse them too: the panel makes those MACs itself.
Export and import CSV#
Use CSV to paste in MACs a provider generated (Hetzner separate MACs, OVHcloud MACs made by hand) or to reserve many addresses at once. It works on public IPv4 and IPv6 blocks, not NAT networks.
Export CSV downloads address,mac,reserved,note,rdns: every address the page lists, in address order. reserved is yes or no; rdns is read only and ignored on import. A cell starting with =, +, -, @, a tab or a carriage return gets a leading ', so a spreadsheet does not run it as a formula; the import removes it again.
CSV columns#
| Column | Values | Notes |
|---|---|---|
address |
an address of the block | Required. Rows are matched by address. |
mac |
02:00:00:ab:cd:ef, 02-00-00-ab-cd-ef, 0200.00ab.cdef or 020000abcdef |
Stored in lower case with colons. Empty clears it. |
reserved |
yes, y, true, 1, reserved, or no, n, false, 0, empty |
Anything else is an error. |
note |
text, up to 1000 characters | Only for a reserved address. |
rdns |
Ignored. |
The file rules:
- UTF-8, with or without a BOM; LF or CRLF line ends; cells separated by
,or;(whichever the first line has more of); CSV quoting, so a quoted note may hold a line break. - Up to 5,000 rows and 1 MB.
- A first line with an
addresscell is a header and names the columns, in any order. Without a header the columns areaddress,mac,reserved,note, and a row may stop early. - A column that is not in the file leaves that value as it is. An empty cell clears it.
- Addresses the file does not name are left alone. An import never deletes anything.
- An IPv4 block already has a row for every address; an address outside it is an error. An IPv6 block takes single addresses of its usable range it has no row for as new free (generated) entries.
Example#
address,mac,reserved,note
198.51.100.10,02:00:00:ab:cd:ef,no,
198.51.100.11,02-00-00-AB-CD-F0,no,
198.51.100.12,,yes,Kept for the mail relay
198.51.100.13,,no,
Row 1 and 2 set fixed MACs (the second is stored as 02:00:00:ab:cd:f0), row 3 reserves an address with a note, row 4 releases an address and clears its MAC.
Without a header, only the first two columns:
198.51.100.10;02:00:00:ab:cd:ef
198.51.100.11;02:00:00:ab:cd:f0
Check and apply#
- On the block's page, click Import CSV.
- Choose a CSV file, or paste the rows into Or paste the rows.
- Click Check the file. Each row is listed as new, changed, unchanged or an error, with the reason.
- Fix any errors and check again. Apply is offered only when no row has an error.
- Click Apply N changes and confirm.
Common errors: "Not in the block", "Bad MAC", "MAC used on another address", "MAC used by a server", "Duplicate in the file", "A note is kept only for a reserved address", "The node's own address stays reserved", and "In use by …" for a row that would change an address a server uses.
The apply runs in one transaction and checks everything again. If anything changed since the check, nothing is applied and you are asked to check the file again. The checked file is kept for 30 minutes. The audit log records one ip_block.imported entry with the counts and the file's SHA-256, never its contents.
Several addresses per server#
A plan's IPv4 addresses field gives each server 1 to 64 addresses (0 for an IPv6-only server). The first is the server's main address; its gateway is the one the server uses. All come from the node's blocks. Every address counts against the account's and its reseller's address limit; NAT and IPv6 addresses do not.
On an existing server, the Network tab lists its addresses, main first. Administrators, and resellers within their limits, use Add address (the next free one, or a chosen one) and Remove for an additional address; the main address cannot be removed. Add IPv6 address works the same way. The node routes the change at once. Inside the server the change takes effect with Reconfigure network, which the page offers right after ("Apply inside the server now? This restarts the server."). A server installed from an ISO must configure its additional addresses itself.
Edit or delete a block#
Edit block changes the name, the DNS servers (for servers created from now on), the reverse DNS account, the note, the address check switch and, for an on-link IPv4 block, its VLAN. For IPv6 blocks it also changes the provider's gateway and the usable range. The network, the gateway and the addresses cannot be changed: servers use them.
Delete block is refused while any address is in use or reserved (the node's own address included). Release them first.
Where addresses are listed#
Servers › Networking lists the addresses of every server the account can see, for every account level: address, version, server, main or additional, gateway and prefix, and reverse DNS name. Administrators filter by account and by block. The API has the same blocks under /ip-pools; see the API reference.