IPv4 and IPv6 on a server

A typical VPS has one public IPv4 address and, if the host supports it, an IPv6 subnet. An extra IPv4 address almost always costs money, and the cheapest plans sometimes come without their own IPv4 at all. Here is where the shortage comes from, what you can do with IPv6 alone and which address settings a mail server needs.

Updated 02.11.2026 · Find a VPS for your needs →

An IP address is a server's number on the internet. In IPv4 it is 32 bits long, giving about 4.3 billion addresses in total, and some of them are reserved for special-purpose and private networks. In IPv6 the address is 128 bits long, and there are so many addresses that a host can give every server an entire subnet. The two protocols run in parallel: a dual-stack server is reachable both by those who have IPv6 and by those who have only IPv4.

Why IPv4 ran out and costs money

Free IPv4 addresses were handed out by five regional registries, each in its own part of the world. Their common pool at IANA ran out on 3 February 2011: on that day the last addresses were split equally between the registries. North America's ARIN exhausted its pool on 24 September 2015. Europe's RIPE NCC handed out its last free addresses on 25 November 2019. Since then a new organisation can join the RIPE NCC waiting list and receive just 256 addresses (a /24) when addresses returned by others come back into the pool.

So a host that needs new addresses buys or leases them from other organisations and either passes the cost into the plan price or charges for an extra address separately. According to the accsly catalog as of 2 November 2026, across 140 hosts that state the price of an extra IPv4 unambiguously, the median is about $2.2 a month per address (180 ₽ at the 2 November 2026 rate), and half of the prices range from about $1.9 to $3.4. A free extra address is a rarity.

Hence a practical tip: if the server needs several addresses — separate sites with their own certificates have not required this for a long time, but it can be needed for mail or for separating services — factor them into the plan price from the start.

NAT VPS and servers without IPv4

To sell servers more cheaply, some hosts do not give each one its own IPv4. There are two variants.

  • NAT VPS: one external IPv4 for several servers, each with its own small range of ports. The host forwards an incoming connection on a port from your range to your server. That is enough for SSH, a bot that calls APIs itself, or tests. You cannot run a website on ports 80 and 443 without an intermediary, and the PTR and the address reputation are shared with the neighbours.
  • IPv6-only: the server has IPv6 addresses only. Incoming connections are possible only from those who have IPv6; outgoing ones only to resources reachable over IPv6.

In the accsly catalog, 349 VPS plans from 31 hosts come without their own IPv4. Buy such a plan only if you understand what the server will do and where connections to it will come from.

IPv6 and the /64 subnet

In IPv6 the address is split in half: the first 64 bits are the network number, the last 64 bits the number of the device within it. This is a requirement of the IPv6 architecture (RFC 4291, discussed in RFC 7421), so the minimum subnet for a single network segment is a /64, and it is not customary to divide it further. In its recommendations for operators (document RIPE-690), RIPE NCC advises giving a customer a /48 or /56, and no less than a /64 per segment.

For a server this means: a /64 holds more than 18 quintillion addresses, and you can put as many IPv6 addresses on one VPS as you need, free of charge. In practice hosts assign them differently — a whole /64, a larger subnet or individual addresses from a shared network — so check the terms if you need many addresses. IPv6 support is confirmed by 703 hosts in the catalog; plans are in the collection VPS with IPv6.

Three commands check that IPv6 works on the server:

ip -6 addr show scope global
ping -6 -c 3 2001:4860:4860::8888
curl -6 -sI https://www.google.com | head -1

The first shows the assigned addresses, the second that the server reaches the outside network over IPv6, the third that DNS and HTTPS work. Do not forget the firewall: IPv4 rules do not automatically apply to IPv6. ufw applies them to both protocols, while with hand-written iptables rules you need a separate ip6tables set. The other hardening steps are in First 10 steps after buying a VPS: security.

When IPv6 alone is enough

An IPv6-only server fits when ordinary visitors do not connect to it directly:

  • internal services — a database, a queue, backup storage — that your own IPv6-enabled servers connect to;
  • a website behind a CDN or reverse proxy: visitors arrive at the CDN's IPv4 address, and the CDN fetches pages from your server over IPv6 — if the CDN provider supports it;
  • test environments and code builds, if all the repositories you need are reachable over IPv6;
  • SSH administration, if you yourself have IPv6 at home or in the office.

It is not enough if visitors connect to the server directly — a website without a CDN, a game server, mail — or if the server itself calls services that have no IPv6: some APIs, package mirrors and websites still work over IPv4 only. For outgoing connections to them there is the NAT64 and DNS64 mechanism (RFC 6146 and RFC 6147): the host or a public service translates requests to IPv4 addresses into IPv6. If the host does not provide it, an IPv6-only server cannot reach such resources.

Reverse DNS (PTR) for mail

An ordinary DNS record maps a name to an address (A for IPv4, AAAA for IPv6). A reverse PTR record maps an address to a name. It matters to mail servers: Google requires senders to have a PTR record for the sending address pointing to a name, and that name in turn must point back to the same address. Without this, mail to Gmail is rejected or lands in spam. The recommendation to keep a matching PTR and A for every address already appears in RFC 1912.

PTR is set by the owner of the address — the host. Usually it is a field in the server control panel or a request to support. The steps:

  1. create an A record (and AAAA if mail will go out over IPv6), for example mail.example.com → the server address;
  2. ask the host, or enter in the panel, a PTR for the same address: address → mail.example.com;
  3. check with dig -x server_address +short — the answer must match the name from the A record;
  4. if the server also sends mail over IPv6, the IPv6 address needs a PTR too, otherwise some messages will go out from an address without a reverse record.

On a NAT VPS you cannot set your own PTR: the address is shared. Another requirement for a mail server is an open outbound port 25: some hosts close it by default and open it on request. Plans where this is possible are in the collection VPS for a mail server. For other plan terms worth checking before you pay, see How to read hosting plans: the hidden limits.

FAQ

Why does an extra IPv4 address cost money?

Free IPv4 addresses have run out: the common IANA pool in 2011, Europe's RIPE NCC in November 2019. Hosts buy or lease addresses from other organisations and charge for them. According to the accsly catalog, the median is about $2.2 a month per address.

What is a NAT VPS?

A server without its own public IPv4: several customers share the external address, each with a range of ports. It suits a bot and tests, but not a website on ports 80 and 443 or a mail server.

What does IPv6 /64 mean?

A subnet in which the first 64 bits of the address are the network number and the last 64 the device number. Under the IPv6 standard it is the minimum subnet for a single network segment, and it holds more than 18 quintillion addresses.

Can I host a website on IPv6 only?

Not directly: visitors without IPv6 will not be able to open it. What works is a setup where the site sits behind a CDN or proxy with an IPv4 address, which fetches pages from your server over IPv6.

Why does a mail server need a PTR record?

Mail services check that the sender's address has a reverse DNS record pointing to a name that resolves back to the same address. Google requires this from all senders; without PTR, messages are rejected or go to spam.

Who sets up PTR?

The owner of the address — the host. PTR is usually set in the server control panel or through a support request. On a NAT VPS you cannot set your own PTR.

Plans on this topic

Best VPS hosting 2026

More in the guide

  • How to read hosting plans: the hidden limitsA plan card shows cores, memory, disk and a monthly price. Yet two plans with identical numbers can cost different amounts a year later and behave differently under load. The difference lies in terms printed in small type, in the acceptable use policy, or only in the contract. Below are eight places worth checking before you pay.
  • Bandwidth and traffic: what 1 Gbps and unlimited really meanA server plan usually has two network lines: port speed and traffic volume. The first says how fast the server can send data, the second how much it can send in a month. They are linked by simple arithmetic, and once you know it, it is easy to see what "1 Gbps unlimited" actually offers and whether "5 TB" will be enough for you.
  • Docker on a VPS: getting startedDocker lets you run a bot, a website, a database and monitoring on one server without them getting in each other's way, and moving to another VPS comes down to copying a couple of files and the data. Installation takes five minutes; the real trouble starts later: database ports exposed to the internet, logs growing to tens of gigabytes and data that vanished along with a container. Here is how to avoid all of that from the start.
  • How to move a website from shared hosting to a VPSThe move itself takes a couple of hours; the mistakes usually happen around it: a forgotten cron job, .htaccess rules that nginx does not read, an AAAA record with the old address, or mail that disappeared along with the IP change. Below is the order of steps with commands and checks for a PHP and MySQL site.
  • Server control panels: ISPmanager, FASTPANEL, aaPanelA panel turns a VPS into the kind of dashboard you know from shared hosting: sites, databases, mail and certificates are set up with a few clicks instead of editing config files. The three panels most often installed on Russian and budget international servers are ISPmanager, FASTPANEL and aaPanel. They differ in price, memory requirements and how much of the server they take over.
  • Windows VPS for 1CA rented server for 1C saves you from the office PC under a desk that nobody updates or backs up. But 1C on a VPS has its own quirks: the software licence is tied to the parameters of the virtual machine, users need both 1C and Windows licences, and core speed matters more than core count. Here is how to put together a 1C server for a small company.
  • Windows VPS: licensing, RDP and secure sign-inA Windows server costs more than Linux not only because of memory: the price includes a licence, and how it is arranged decides whether you are compliant and how many people can connect. An exposed RDP port is also the most common way such servers get hacked. Here are both topics.
  • When to move from shared hosting to a VPSA VPS does not make a site faster by itself: it gives you resources and freedom, and with them the job of running a server. Here is how to tell that hosting has become too small, when the problem can be solved without moving, and how to migrate a site so visitors notice nothing.
  • VPS backups: strategies and toolsOn a VPS, backups are your job, even if the plan says "backups included". We go through what exactly to back up, why a host snapshot is not enough, how to set up restic or BorgBackup in half an hour, and how to make sure you can actually restore from a backup.
  • First 10 steps after buying a VPS: securityBots start guessing passwords on a new server within minutes of it getting a public IP. Below are ten steps that close the most common holes in about an hour: commands for Ubuntu and Debian, the differences for AlmaLinux and Rocky Linux, and the checks that keep you from locking yourself out of your own server.
  • How to choose a country for your serverPut the server where your visitors are. For an audience across Europe, Germany, the Netherlands and Finland are convenient; for North America, the US East Coast. If you serve EU users, keeping the data in the EU makes GDPR simpler. Price hardly decides it: at the same host a server in Frankfurt, Amsterdam or New York usually costs the same, and only Asia and Australia are noticeably more expensive.
  • Hourly billing: when it pays offHourly billing pays off if you need the server for less than three weeks a month: for a test, a build, a one-off heavy job. At most hosts an hour costs exactly the monthly price divided by 730 hours, so over a full month you hardly overpay. The overpayment hides elsewhere: hourly plans are dearer on average, and for a server that runs all year, monthly billing or a year paid in advance usually comes out cheaper.
  • How much RAM and how many cores a website needsMost websites are fine with 2 GB of memory and one or two cores; a shop with thousands of products needs 4 GB and two cores. Memory matters more than cores: when it runs out, the site slows down or crashes, while an extra core without memory adds almost nothing. Below I show how to work out the memory for your site and how to see what it actually uses.
  • KVM or OpenVZ: which to chooseIn 2026 KVM is almost always the right pick: it costs a dollar or two more per month than OpenVZ, but everything runs on it, from Docker to Windows. OpenVZ makes sense in one narrow case, explained below, and at the end you will find the commands to check your own server in a minute.
  • NVMe or SSD: does it matter for a websiteFor a small site the difference between NVMe and SSD is barely noticeable, because pages are served from memory rather than from disk. It shows up in shops and sites with a large database. At the same host NVMe costs only about $0.50–1 a month more, and sometimes less, so what usually decides it is not the disk type but its size and how the host has limited it.
  • What is a VPS, in plain EnglishA VPS is a slice of a powerful physical server that you rent and that behaves like a separate computer, with its own operating system, its own IP address and full control. Below is how it differs from shared hosting, who needs one, what it costs and what to check right after you buy it.
  • VPS for a Telegram bot: what the bot needs and how to pick a planA bot with a menu and a few commands runs fine on the cheapest server, while a bot with broadcasts, files and a database hits completely different limits. Here is what a bot really consumes, which Telegram limits shape the choice of server and how to avoid overpaying.
  • How to test VPS ping and speed before you payThe numbers in a plan do not tell you the latency to your users or how fast the disk really is. Most of this can be measured before you pay, the rest in the first hour after launch. Here are the tools and how to read the results.
  • Corporate network on a VPS: remote access to the officeA rented server can become the hub of a company's private network: remote employees and branch offices connect through it to the ERP, file server, CRM and Git. Here are the common layouts, protocols, server requirements and security basics.
  • How to choose a VPS: the 7 specs that matterTwo plans with the same "2 cores, 4 GB, 50 GB" can differ several times in speed and twice in price a year later. Here is what stands behind each line of a VPS plan and what to check before you pay.
  • VPS vs VDS: is there a difference and what actually mattersIn most markets VPS and VDS mean the same thing: a virtual server. The difference that really affects your work is hidden not in the name but in the virtualization type and whether resources are guaranteed.