AAAA Records and IPv6 for Hosting – What You Need to Know

The internet ran out of IPv4 addresses years ago. The replacement, IPv6, has been deployed slowly but is now serving 40-50% of major network traffic. Sites without IPv6 (AAAA records) work for IPv6-only visitors only via translation layers that add latency and points of failure. This guide explains AAAA records, when to add them, and the dual-stack approach where your site responds to both IPv4 and IPv6.

IPv4 vs IPv6 — the basics

• IPv4 — Old standard. 32-bit addresses (e.g. 192.0.2.1). About 4.3 billion possible. Exhausted.
• IPv6 — New standard. 128-bit addresses (e.g. 2001:db8::1). Effectively unlimited supply.
• Dual stack — Server responds to both. Most modern sites and ISPs.

IPv4 isn’t going away — most of the internet still runs on it. But IPv6 adoption keeps growing, especially in mobile networks (Reliance Jio in India, T-Mobile US, many African mobile networks).

DNS record types

• A record — Maps domain to IPv4 address.
• AAAA record — Maps domain to IPv6 address. Pronounced “quad-A.”

Both can coexist for the same domain. Browser asks for both; uses whichever protocol it has (or whichever performs better — “happy eyeballs” algorithm).

When you need AAAA records

• Mobile-heavy audience in countries with heavy IPv6 deployment.
• Best-practice modern web — having both is the default expectation.
• You want to be reachable when IPv4 has issues at intermediate networks.
• Email server — Major mail providers test IPv6 reverse DNS for trust.

When AAAA records cause problems

• Your server doesn’t actually have IPv6. AAAA record points to address; visitor connects; server doesn’t respond on that address. Site appears broken for IPv6 users.
• Firewall blocks IPv6 connections. Same effect — site doesn’t respond.
• Web server not configured to listen on IPv6. Apache/Nginx needs explicit IPv6 binding.

Adding AAAA without verifying full IPv6 readiness creates problems worse than no IPv6 at all.

Checking if your server has IPv6

Via SSH

# See IPv6 addresses on server
ip -6 addr show

# Test outbound IPv6
curl -6 https://ifconfig.co

# Test you can be reached
ping6 ipv6.google.com

External check

Tool: ipv6-test.com — tests your site from IPv6 networks.

Or: dig AAAA yourdomain.com — if returns IPv6, AAAA record exists.

cPanel

cPanel → Account Information → may show dedicated/shared IP addresses. If IPv6 is allocated to your hosting, it’ll be listed (usually starting with 2001: or 2a02: etc).

Adding an AAAA record

1. Get your IPv6 address from server provider or cPanel.
2. cPanel → Zone Editor.
3. Add Record → Type: AAAA → Name: yourdomain.com (or @) → Address: your IPv6 → Save.
4. Add another AAAA for www subdomain.
5. Wait for DNS propagation (typically minutes).

Web server config

Server must listen on IPv6 too. On managed cPanel with LiteSpeed/Apache, usually automatic if IPv6 allocated.

On VPS where you control config:

• Apache: Listen [::]:80 and Listen [::]:443 in main config.
• Nginx: listen [::]:80; and listen [::]:443 ssl; in server block.

Restart web server. Verify with: netstat -tlnp | grep -E ':80|:443'

SSL certificates and IPv6

AutoSSL (Let’s Encrypt) works with IPv6 properly when:

• Both A and AAAA records exist.
• Server responds on both protocols.
• HTTP-01 challenge can reach over either.

If AAAA points to wrong address or server doesn’t listen on IPv6, AutoSSL may fail challenges. Either fix IPv6 or remove AAAA record.

Cloudflare and IPv6

If your domain is behind Cloudflare:

• Cloudflare provides IPv6 at the edge regardless of your origin’s protocol support.
• Your origin only needs IPv4 (Cloudflare connects to you over v4 if v6 not available).
• Cloudflare → Network → IPv6 Compatibility — enable.
• Visitors get IPv6 connectivity even if your hosting doesn’t have it.

This is the easiest way to add IPv6 if your server doesn’t support it natively.

IPv6 for email servers

Mail-specific considerations:

• MX record — Points to hostname, not IP. Doesn’t change.
• Reverse DNS (PTR) for IPv6 — Critical. Without it, Gmail/Microsoft reject mail from your IPv6.
• SPF — Include IPv6 ranges if sending from them.

For mail servers without proper IPv6 setup, often best to NOT send mail over IPv6 — configure server to use IPv4 outbound only.

Testing IPv6 access

• From command line: curl -6 -v https://yourdomain.com
• Online: ipv6-test.com — runs tests against your domain.
• Hurricane Electric’s tunnelbroker.net provides free IPv6 tunnels for testing.
• Modern mobile networks often IPv6-only — try from phone using mobile data.

Common questions

“Does adding AAAA hurt my IPv4 visitors?” No. They use the A record as before. AAAA is only for IPv6 capable clients.

“My iWebVault shared hosting — does it have IPv6?” Varies by server. Open a ticket to confirm IPv6 availability on your specific server.

“How do I know if visitors are using IPv6?” Server access logs show IP. IPv6 addresses are easy to spot (colons, longer). For statistics: Cloudflare analytics, AWStats, plugins.

“My ISP doesn’t have IPv6 — am I missing out?” As a visitor, no — IPv4 is still fully supported. As a publisher, modern best practice is dual-stack support.

“Should I use IPv6 only?” Almost never. Most consumer networks still don’t have IPv6 (though percentage rises every year). IPv6-only excludes IPv4-only visitors.

“DNS provider charges extra for AAAA?” No legitimate DNS provider does. Same record type, no different cost.

What’s next

• DNS basics: DNS records overview.
• Cloudflare for IPv6 layer: Cloudflare.
• Reverse DNS: PTR records.

IPv6 adoption is no longer optional for forward-looking sites. Adding AAAA records is straightforward IF your server actually supports IPv6 — verify first, configure server to listen, then add the record. If your hosting doesn’t have native IPv6, Cloudflare’s free tier provides IPv6 edge connectivity transparently. Either way, the goal is dual-stack: visitors over IPv4 and IPv6 both reach your site without delays or detours.