IPv4 vs IPv6 for Servers: A and AAAA Records

How servers publish IPv4 and IPv6, when mapped addresses matter, and how to convert or compare address families with PINIP tools.

Two address families, two DNS records

Modern servers often listen on both IPv4 and IPv6. DNS publishes them separately: A for IPv4 and AAAA for IPv6. Clients prefer IPv6 when available (Happy Eyeballs), but many networks are still IPv4-only.

PINIP’s Domain to IP tool shows both. The IPv4 ↔ IPv6 converter expands/compresses IPv6 and shows IPv4-mapped forms (::ffff:x.x.x.x).

What does not convert

A native public IPv6 address is not “the same number” as an IPv4 address. There is no universal one-to-one mapping. Only IPv4-mapped IPv6 embeds a specific IPv4. To relate families for a website, always go through DNS for that hostname.

Server ops tips

  • Publish AAAA only when the service is actually reachable on IPv6 end-to-end.
  • Monitor both families in uptime checks — IPv6-only failures are common.
  • After changing DNS, re-check with Domain to IP and the full IP Lookup.

FAQ

Can PINIP convert any IPv6 to IPv4?

Only IPv4-mapped addresses expose an embedded IPv4. Native IPv6 needs DNS or application context.

Should every server enable IPv6?

If your users and upstream support it, yes — but test thoroughly before publishing AAAA records.

← All guides