Skip to main content

AAAA Record Lookup (IPv6)

Check your domain's IPv6 address in seconds

Site not accessible over IPv6? Check if your AAAA record is correctly published and propagated across global DNS resolvers.

In iterative trace mode, the resolver is ignored.
Query multiple public resolvers to compare answers.

Instant resolution

Get a domain's IPv6 address in real-time. Verify dual-stack configuration with A and AAAA records.

Multi-resolver

Compare responses from Google, Cloudflare, and Quad9 to detect propagation issues.

Iterative trace

Follow the complete resolution path from root servers to the final answer.

TTL and latency

View the cache duration and response time for each queried resolver.

Free and unlimited

Test as many domains as needed. No signup required.

How to use the DNS lookup engine options effectively

What is the iterative trace?

The trace performs resolution step by step. The resolver first queries the root servers, then the TLD (.com, .fr, .eu), and then the authoritative servers of the target zone. At each step, the page shows the queried server, the answer, the RCODE, and the latency.

  1. 1. Root

    Discovery of the TLD servers for the requested name.

  2. 2. TLD

    Reference to the zone's NS (delegation).

  3. 3. Authoritative

    Final answer (or error) with TTL and latency.

What is it for?

  • Compare answers across resolvers and regions
  • Detect a hot cache, an overly long TTL, or an incomplete delegation
  • Explain a latency difference or an unexpected RCODE

Tip: keep the trace disabled for quick checks; enable it when investigating or preparing a ticket/post‑mortem.

What is the classic trace?

The classic trace queries only the selected resolver (UDP or DoH) and displays the answer as it is perceived from that network vantage point. You get the RCODE, the response sections, and the latency for the client → resolver leg.

  1. 1. Chosen resolver

    Uses the preset or custom configuration to run the query exactly like your service would.

  2. 2. Protocol preserved

    Respects the selected transport (UDP, TCP, or DoH) so you reproduce the real behaviour.

  3. 3. Detailed answer

    Shows the question, answer, and authority/additional sections when present, together with TTL and useful metadata.

Why use it?

  • Check the view of a specific resolver before suspecting delegation issues
  • Confirm cached values and the impact of a TTL or a flush
  • Document a resolution exactly as a client or microservice sees it

Tip: keep the iterative trace option turned off when auditing a given resolver; enable it afterwards to compare with the root → TLD → authoritative path.

How does the propagation test work?

The test queries a set of public resolvers (Google, Cloudflare, Quad9, OpenDNS, ISPs…) in parallel and groups the answers by content and RCODE. You instantly see who already picked up the update.

  1. 1. Multi-point resolvers

    Enables the propagation presets to question several actors spread around the world.

  2. 2. Automatic comparison

    Groups identical answers and highlights divergences or resolver-specific errors.

  3. 3. Actionable summary

    Provides a clear recap, the resolver list, their latencies, and each group's status.

When to use it?

  • Track how a DNS change propagates worldwide
  • Spot stale caches and decide on a targeted flush
  • Share a propagation snapshot in a ticket or post-mortem

Tip: while the propagation test is active, the resolver selector is frozen. Disable the mode to return to single-resolver diagnostics.

What is an AAAA record?

An AAAA record (pronounced "quad-A") associates a domain name with an IPv6 address. It's the IPv6 equivalent of the A record used for IPv4.

AAAA record structure:

FieldDescriptionExample
NameThe domain or subdomain@ or www
TypeAlways AAAAAAAA
ValueIPv6 address2001:db8::1
TTLCache duration in seconds3600

Dual Stack Configuration

The recommended configuration combines A and AAAA for the same name:

captaindns.com.  3600  IN  A     93.184.216.34
captaindns.com.  3600  IN  AAAA  2001:db8::1

Dual stack advantages

AdvantageDescription
Better connectivityAccessible from both IPv4 and IPv6 networks
Automatic fallbackHappy Eyeballs chooses the best connection
Future-proofingIPv6 is gradually becoming predominant

IPv6 Address Format

An IPv6 address contains 128 bits represented as 8 groups of 4 hexadecimal characters:

2001:0db8:85a3:0000:0000:8a2e:0370:7334

Abbreviated notation

RuleExample
Leading zeros in groups0db8 → db8
Consecutive zero groups:: (only once)
Compact form2001:db8::8a2e:370:7334

Best Practices

Configuration

PracticeWhy
Always with ADual stack for maximum compatibility
Same TTL as AConsistent propagation
Routable addressNo private or link-local addresses

Email

PracticeWhy
AAAA on MX hostsIPv6 support for receiving emails
IPv6 PTR configuredImproves deliverability
SPF includes IPv6Authorizes sending from IPv6

Common Issues

Site inaccessible on IPv6 only

  1. Verify the AAAA record exists
  2. Check the address is publicly routable
  3. Verify the server listens on IPv6

Incorrect IPv6 address

  1. Verify syntax (8 groups or valid abbreviated notation)
  2. No spaces or invalid characters
  3. Address provided by your host

Slow propagation

  1. Wait for the previous TTL to expire
  2. Test with different resolvers
  3. Check authoritative servers

Command Line Verification

Linux/Mac

dig AAAA captaindns.com

Specific resolver:

dig AAAA captaindns.com @8.8.8.8

Windows

nslookup -type=aaaa captaindns.com

IPv6 connectivity test

ping6 captaindns.com

or

ping -6 captaindns.com

AAAA and Cloud Services

Most cloud providers support IPv6:

ProviderIPv6 Support
AWSYes (ELB, CloudFront, EC2)
Google CloudYes (Load Balancer, CDN)
CloudflareYes (automatic proxy)
AzureYes (Load Balancer, CDN)
ToolPurpose
A Record LookupCheck IPv4 address
DNS Propagation CheckCheck worldwide propagation
PTR Record LookupCheck IPv6 reverse DNS

Useful resources