Skip to content
AdminKit

Dual-stack

What is Dual-stack?

Dual-stack is a network configuration where a device or network runs IPv4 and IPv6 at the same time, each needing its own security configuration, as defined in RFC 4213. AdminKit's DNS lookup tool resolves both a domain's A (IPv4) and AAAA (IPv6, RFC 3596) records side by side for a dual-stack audit.

By AdminKit team, Netbase JSC · Updated

Dual-stack is a network configuration where a device or network runs IPv4 and IPv6 at the same time, each with its own address, rather than only one. RFC 4213 (see its IETF Datatracker entry for the RFCs that have since updated it) defines this as the basic transition mechanism for IPv6 deployment: a dual-stack host can reach an IPv4-only destination over IPv4 and an IPv6-only destination over IPv6, using whichever protocol a given DNS lookup and route actually support. Most consumer ISPs and routers run dual-stack today rather than switching to IPv6-only, since plenty of destinations and internal services remain IPv4-only. Desktop and server operating systems are built for it too: Microsoft’s guidance on configuring IPv6 in Windows says Windows favors IPv6 global unicast addresses over IPv4 by default and recommends preferring IPv4 through prefix policies rather than disabling IPv6, since some Windows components might not function without it. The practical catch is that security has to be configured for both stacks separately — a firewall rule written only for IPv4 silently leaves the same device’s IPv6 address unprotected, a risk NIST’s own IPv6 deployment guidelines call out explicitly. AdminKit’s DNS lookup tool reflects this by resolving both a domain’s A (IPv4) and AAAA (IPv6) records side by side. See the AAAA record entry for how that IPv6 address record is defined and why RFC 3596 added it alongside the older A record. When a destination publishes both, Happy Eyeballs decides which address family a dual-stack client actually connects over first, rather than leaving it to chance. Older transition mechanisms like Teredo and 6to4 took a different approach, tunneling IPv6 inside IPv4 rather than running both natively, and are now considered legacy next to native dual-stack.

Dual-stack is part of AdminKit’s IP & network cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

What does dual-stack actually mean for a device or network?

That it runs IPv4 and IPv6 at the same time, each with its own address, rather than running only one protocol.

Why do most consumer ISPs still run dual-stack instead of IPv6-only?

Because plenty of destinations and internal services remain IPv4-only, so an IPv6-only network alone wouldn't reach everything a dual-stack one can.

What's the practical security catch with dual-stack?

Security has to be configured for both stacks separately -- a firewall rule written only for IPv4 silently leaves the same device's IPv6 address unprotected.

What decides which address family a dual-stack client connects over first?

Happy Eyeballs, when a destination publishes both an A and AAAA record, rather than leaving it to chance.