An AAAA record, sometimes called a quad-A record, is a DNS record that points a domain name or subdomain to an IPv6 address. It performs the same role for IPv6 that an A record performs for IPv4. When someone visits a domain, the AAAA record helps direct that request to the correct server if that service is reachable over IPv6.

For Apexhost customers, AAAA records are most often used when connecting a domain or subdomain to a hosting service, server, firewall, application, or other internet-facing service that has an IPv6 address. Understanding how AAAA records work can help you manage DNS more accurately, especially in environments that support both IPv4 and IPv6.

DNS, or Domain Name System, acts like the internet’s address book. People use domain names such as example.com, but computers communicate using IP addresses. An AAAA record links a readable domain name to a destination IPv6 address.

For example, if www.example.com has an AAAA record that points to 2001:db8::10, a user whose network supports IPv6 may be directed to the server using that IPv6 address.

An AAAA record is used for IPv6 only. If the service uses an IPv4 address instead, the equivalent DNS record type is an A record.

In simple terms, an AAAA record tells the internet which IPv6 address a domain name should use.

AAAA records are used in a range of common DNS scenarios, including:

• Pointing a root domain such as example.com to a server with a public IPv6 address

• Pointing a subdomain such as www.example.com or app.example.com to an IPv6-enabled service

• Supporting modern dual-stack environments where a service is available over both IPv4 and IPv6

• Connecting a domain to an external platform or infrastructure provider that supplies an IPv6 destination

• Moving a website or service to a new IPv6-enabled server by updating the DNS destination

Before changing an AAAA record, make sure you know which DNS service is authoritative for the domain. Updating DNS in the wrong control panel will not affect live traffic.

An AAAA record usually contains the following parts:

• Name / Host — the domain or subdomain being pointed, such as @, www or app

• Type — AAAA

• Value / Points to / Address — the destination IPv6 address, such as 2001:db8::10

• TTL — Time To Live, which controls how long resolvers may cache the record before checking again

The exact labels may vary depending on the DNS platform, but the purpose is the same.

Common examples include:

• @ → 2001:db8::10

• www → 2001:db8::10

• app → 2001:db8:1::25

In many DNS editors, @ represents the root domain, also called the apex domain.

Before adding or changing an AAAA record, make sure you have:

• Access to the correct DNS management portal for the domain

• Permission to update the domain’s DNS records

• The correct IPv6 address provided by your hosting provider, server administrator, website platform or network team

• A copy of the existing DNS settings in case you need to revert the change

• An understanding of whether the change applies to the root domain, a subdomain, or both

DNS changes can affect website availability and other connected services. If you are unsure which record should be changed, review the existing configuration carefully before saving any updates.

1. Log in to the DNS management portal or control panel that hosts the domain’s DNS zone.

2. Open the DNS management area for the domain you want to update.

3. Review the existing DNS records to identify whether an AAAA record already exists for the host name you want to use.

4. If an AAAA record already exists for that host name, edit the existing record rather than creating a duplicate unless your provider specifically requires multiple AAAA records.

5. Enter the host name, such as @ for the root domain or www for a common web subdomain.

6. Select AAAA as the record type.

7. Enter the destination IPv6 address supplied for the service.

8. Set the TTL if needed, or leave the default value if you have not been given a specific requirement.

9. Save the record.

10. Allow time for DNS caches to update before testing from all networks.

[Screenshot: DNS zone editor showing an AAAA record for the root domain]

[Screenshot: DNS zone editor showing an AAAA record for the www subdomain]

After the record is saved, traffic for that host name should begin resolving to the specified IPv6 address once DNS propagation and caching delays have passed.

Updating the root domain does not always update the www subdomain automatically, and updating www does not always update the root domain. In many DNS zones these are separate records.

For example:

• example.com may point to one IPv6 address

• www.example.com may point to the same address or a different one

If you want both addresses to load the same website, make sure the relevant DNS records are configured accordingly.

TTL stands for Time To Live. It tells DNS resolvers how long they can cache a record before requesting a fresh copy. A shorter TTL may allow changes to be seen sooner by some resolvers, while a longer TTL may reduce lookup frequency.

Even after you save a new AAAA record, not every user will see the change immediately. DNS propagation is the general term used to describe the time it takes for cached results across different networks and resolvers to refresh.

Propagation time varies depending on the previous TTL, the resolver being used, local device caching and the DNS provider. Because of this, a change may appear correct from one network while another still sees the old destination for a period of time.

• Entering the wrong IPv6 address

• Updating DNS in a control panel that is not authoritative for the domain

• Creating duplicate records for the same host without intending to use DNS round-robin behaviour

• Forgetting to update both the root domain and www where required

• Replacing an important existing record without recording the original value first

• Expecting DNS changes to apply instantly everywhere

• Confusing AAAA records with A, CNAME or MX records

This usually means DNS caching is still in effect somewhere between the DNS provider, internet service provider, local network or device.

Check that the AAAA record was saved in the correct DNS zone, confirm the entered IPv6 address is correct, and allow additional time for propagation.

This may happen if the new IPv6 address is incorrect, the destination server is not configured for the domain, or the service is not listening properly over IPv6.

Review the current AAAA record value, compare it with the intended server details, and confirm the hosting or service at the destination IPv6 address is configured to respond for that domain name.

If the domain uses external nameservers or another DNS host, changes made in a local hosting panel may not affect live DNS.

Check which nameservers are active for the domain and confirm where the authoritative DNS zone is managed before making further changes.

Some networks, devices or providers may not fully support IPv6, or may prefer IPv4 when both are available. This can make testing appear inconsistent.

If the service is intended to support both protocols, check whether A and AAAA records are both configured correctly and verify that the server is reachable over IPv6 from external networks.

If the destination is another hostname rather than a direct IPv6 address, you may need a CNAME record instead of an AAAA record. The correct record type depends on the service you are connecting.

What is the difference between an A record and an AAAA record?

An A record points to an IPv4 address. An AAAA record points to an IPv6 address.

Can I have more than one AAAA record for the same host name?

Yes. Some services use multiple AAAA records for redundancy or load distribution. However, you should only do this when you understand the intended behaviour and the service supports it.

Do I need an AAAA record if I already have an A record?

Not always. If your service only uses IPv4, an A record may be enough. If your server or platform supports IPv6 and you want the domain to resolve over IPv6 as well, you can add an AAAA record.

Does changing an AAAA record affect email?

Not directly in most cases, because email routing usually depends on MX records. However, related services may still be affected if the same host name is used elsewhere or if other connected DNS records are changed at the same time.

• What is DNS? (DNS)

• A Records (DNS Records)

• DNS Records (DNS)

• Change DNS records

• Domain Names Explained (Domains)

If you require further assistance, please contact Apexhost Support at support@apexhost.com.au.