IPv6-only VPS: savings and limitations
A host buys or leases each IPv4 address, so a server with IPv6 only is usually cheaper — by a dollar or two a month. But such a server cannot see part of the internet, and users without IPv6 cannot connect to it. Here is where the saving makes sense and what to check before you pay.
The short answer. An IPv6-only VPS suits back-office tasks: backups, an internal database, a test environment, a node that only your own servers connect to. It is not suitable for a public website without an intermediary: visitors without IPv6 will not be able to open it. Before buying, check that every service the server itself connects to is reachable over IPv6.
How much you save by giving up IPv4
In the accsly.io catalog on 16 November 2026, 481 VPS plans at 35 hosts come without their own IPv4 address; for 184 plans at 13 hosts this is stated right in the name. 677 VPS hosts state IPv6 support. Prices of identical plans with and without IPv4, as recorded in the catalog, per month:
| Host and plan | IPv6 only | With IPv4 |
|---|---|---|
| AWS Lightsail, Linux, 0.5 GB | $3.5 | $5 |
| AWS Lightsail, Linux, 2 GB | $10 | $12 |
| AWS Lightsail, Linux, 64 GB | $380 | $384 |
| Vultr, 1 vCPU, 0.5 GB | $2.5 | $3.5 |
| JustHost, Sirius | $6.02 | $8.09 |
| nonic, 8 GB | £4.49 | £5.99 |
The saving is a fixed amount per address, so it is noticeable on small plans: for Lightsail 0.5 GB it is 30% of the price, for 64 GB about 1%. Performance within each pair is the same: Amazon states plainly that IPv6-only plans have a different price but the same CPU baseline (what a baseline and burst are is covered in A host's plan grid: vCPU, fair use and burst). Why IPv4 is scarce and how much an extra address costs is covered in IPv4 and IPv6 on a server.
What does not work without IPv4
A server with IPv6 only can open a connection only to hosts that have an IPv6 address (a DNS AAAA record). A check with dig on 16 November 2026 showed that github.com, api.github.com, codeload.github.com and the ghcr.io image registry have no AAAA record. This means git clone from GitHub and downloading releases and images from there do not work directly. The same goes for the main Amazon S3 address s3.amazonaws.com — S3 has separate dual-stack addresses for this, such as s3.dualstack.us-east-1.amazonaws.com. Check the storage endpoint of other S3 providers in advance too — more in S3 object storage at hosts.
The Debian, Ubuntu and Alpine mirrors, PyPI, npm, Packagist, the Docker Hub registry, GitLab.com and Let's Encrypt are reachable over IPv6. But every project has its own list of dependencies: a module, a licence server or a payment system API may be IPv4-only. Incoming connections are a separate problem: a user whose ISP has no IPv6 will not reach the server at all.
NAT64 and DNS64
To let an IPv6 server reach IPv4 resources, there are NAT64 (RFC 6146) and DNS64 (RFC 6147). For a site without an AAAA record, DNS64 returns a synthetic IPv6 address — usually from the 64:ff9b::/96 prefix (RFC 6052), and a NAT64 gateway translates the connection to IPv4. Some hosts provide their own NAT64 in the network of their IPv6-only plans — ask support about it before buying. Public NAT64 gateways exist too, but then your traffic goes through someone else's server, and its speed and availability are out of your hands.
Checking whether DNS64 works on the server is easy: run dig AAAA ipv4only.arpa. This special name has only IPv4 addresses (RFC 7050), so if the answer contains an IPv6 address, it was synthesized by DNS64, and the beginning of the address is your network's NAT64 prefix. An empty answer means there is no DNS64 and IPv4 resources are unreachable for the server.
How to serve IPv4 visitors
A website on an IPv6-only server can be opened to everyone through an intermediary with IPv4: a CDN or reverse proxy accepts visitors on its own IPv4 address and fetches pages from your server over IPv6. Before doing this, make sure the chosen CDN can connect to the origin over IPv6 — more on this in CDN: when a website needs one. Clients with both protocols will manage on their own: browsers use the Happy Eyeballs algorithm (RFC 8305) to try addresses in parallel with a delay of about 250 ms and pick the one that answers.
Running a mail server on IPv6 only is risky: not every recipient's mail server has IPv6, and mail to them will not go out without IPv4. PTR rules and address reputation are covered in Mail server on a VPS: SPF, DKIM, DMARC.
Who it suits and who it does not
| Task | IPv6-only | Why |
|---|---|---|
| Backup storage | Suitable | Your own servers with IPv6 connect to it |
| Test environment, builds | Suitable with caveats | If all dependencies are reachable over IPv6 or the host has NAT64 |
| Website | Only behind a CDN or proxy | Visitors without IPv6 cannot open the server directly |
| Bot that calls an API | Check the API | The server must reach the API over IPv6 |
| Mail server | Not suitable | Not all recipients accept mail over IPv6 |
If the task changes later, many hosts let you add IPv4 to the server. But then the saving disappears: an extra address often costs more than the difference between the plans. So work out in advance whether the server will need IPv4 within the next year.
What to check before buying
- List the addresses the server connects to itself: repositories, image registries, APIs, backup storage. Run dig AAAA for each — an empty answer means you cannot do without NAT64.
- Make sure you have IPv6 at home or in the office; otherwise you will only be able to connect over SSH through another server.
- Ask the host about NAT64 and whether IPv4 can be added later without reinstalling.
- Take a plan with hourly billing and test installing your project within an hour.
Plans with IPv6 are collected in the VPS with IPv6 selection. The first security settings are the same for both protocols, but firewall rules for IPv6 are set separately — see First 10 steps after buying a VPS: security.