# Network and IP addresses

> Additional IP addresses from any provider, a site's own address or a shared one, and floating IPs ordered from Hetzner.

**Network** (under **System** on the server page) lists every address the server answers on and lets you add more.

## The server's addresses

The server reports the addresses on its network interfaces itself (labelled **On the server**). Each row shows the interface and the sites that use the address; an address no site claims is **shared by every site**.

## Add an address from any provider

Most providers can route extra addresses to a server: a failover IP, a floating or reserved IP, an address from an additional subnet. This works the same wherever your server runs:

1. In your provider's panel, order the address and assign or route it to this server.
2. In Zefily, open **Network → Add an IP address**, enter the **Address** (IPv4 or IPv6), the **Prefix** if your provider gave one (empty means a single address: /32 or /128) and an optional **Label**.
3. Zefily puts the address on the server's main network interface right away and keeps it there after every reboot. It shows as **being applied** until the server reports it.

Zefily only ever adds and removes the addresses you added here; addresses the server already had are never touched. An address that sites use cannot be removed: give them another one first.

## Get an address from your cloud provider

For servers created through a connected **Hetzner** account, **Get address** orders a new floating IP (IPv4, or an IPv6 /64 of which the server takes the first address) for this server, routes it here and puts it on the interface. Hetzner bills it to your own account; removing it in Zefily gives it back to Hetzner. For other providers, order the address in their panel and add it as above.

## Give a site its own address

Open the site, then **Access → IP address**, and pick an **IPv4** and/or **IPv6** address of the server. The web server then serves the site on that address — whatever the site runs: PHP, static files, Node.js, Python, containers or a reverse proxy. Requests that reach that address are served by this site (and any other site you give the same address); the other sites stay on the shared addresses.

- **Shared (every address)** puts the site back on all addresses.
- Several sites can share one added address — useful when a group of sites should sit behind one IP.
- Point the site's DNS records at its own address.
- A site's own address needs nginx: OpenLiteSpeed serves every site on every address.

## After a reinstall

[Reinstalling a cloud server](/docs/server-overview) keeps its additional addresses: they go back on the interface as soon as the fresh system is set up.

---
Source: https://zefily.com/docs/network-and-ip-addresses