IPv4 vs IPv6: What Self-Hosters Need to Know
IPv4 addresses are running out. IPv6 is the future. Here's what changes for self-hosting and what you need to do.
The IPv4 Exhaustion Problem
IPv4 has ~4.3 billion addresses. They're all allocated. New servers increasingly get IPv6 addresses, and some providers charge extra for IPv4.
IPv4 vs IPv6
IPv4
IPv6
Impact on Self-Hosting
DNS
IPv6 uses AAAA records instead of A records. For maximum compatibility, set up both:
Firewall
IPv6 requires separate firewall rules. Don't forget to configure ip6tables alongside iptables.
SSL
No difference. SSL/TLS works the same on both protocols.
Reverse Proxy
Caddy and Nginx handle both protocols seamlessly. No configuration changes needed.
Docker/Podman
Container networking supports IPv6 but often requires explicit configuration. Most setups work fine with IPv4-only internal networking.
Dual-Stack Setup
The recommended approach: support both IPv4 and IPv6.
1. Ensure your server has both IPv4 and IPv6 addresses
2. Configure DNS with both A and AAAA records
3. Configure your firewall for both
4. Your reverse proxy handles the rest
Clients that support IPv6 use it. Clients that don't fall back to IPv4.
Cloudflare as IPv6 Proxy
If your server only has IPv4, Cloudflare can still serve IPv6 clients. Enable proxy mode and Cloudflare handles the protocol translation.
TinyPod Servers
TinyPod servers include both IPv4 and IPv6 addresses. All applications are accessible over both protocols with no configuration needed.